encType, IE adding a encType to form method post |
encType, IE adding a encType to form method post |
JGreene |
Jun 4 2018, 12:52 PM
Post
#1
|
Group: Members Posts: 4 Joined: 4-June 18 Member No.: 26,653 |
Fairly new to all of this and this problem has got me baffled. I have a test and a production system that are not acting the same. I have a web page that is using a simple send_mail.php program. I have the normal three boxes for entering text. NAME, Email address, Comments. And I have coded placeholder with those labels so they show in the boxes. With my test system these labels show up and the php works and I get my email.
With my production system, these labels don’t show up in Internet Explore. In Chrome and Firefox the do. In IE when I go to the Developer Tools. I see a encType added to my form code. This is in the production system. It doesn’t show up in the test system. Here is that code from my production system <form action=”send_mail.php” encType=”application/x-www-form-urlencoded” method=”post”> I guess I don’t understand where the encType came from and why it shows only in the production system with IE. I first thought it was my http.conf file but I believe test and production are the same. I thought it was the mime file but I believe these are the same. The php.ini is the same and the html and css is the same along with the PHP program. I would be grateful for any insight to this. |
JGreene |
Jun 4 2018, 02:16 PM
Post
#2
|
Group: Members Posts: 4 Joined: 4-June 18 Member No.: 26,653 |
So I’ve been playing around a bit. In IE I pulled up both pages, one for test and one for prod. I went into the Developer Tools on both. Under the DOM Explore on the right hand side is a pull down menu with the browser options. Edge, 10 – 5, minus 6. On the prod side the default is 7 and on the test the default is Edge. If I change the numbers (not the default) both work with Edge and 10 and not work with 9 and below. So if I think everything is the same for prod and test why is the default different and how to fix it? |
Christian J |
Jun 4 2018, 02:39 PM
Post
#3
|
. Group: WDG Moderators Posts: 9,656 Joined: 10-August 06 Member No.: 7 |
On the prod side the default is 7 and on the test the default is Edge. Could it be that the production site server sends a X-UA-Compatibility directive to force IE7 rendering? This can be done both with META tags and a HTTP header, see https://msdn.microsoft.com/en-us/library/ff...5(v=vs.85).aspx EDIT: Posted the above before I saw you last reply... QUOTE For production I had the site url in compatibility mode. Never heard of doing that through the URL, but it should indeed explain it. QUOTE I’m not experienced enough to know what to do if users to the site have IE and have this site’s url in their Compatibility View Settings. That sounds like a power user intentionally manipulating the site, then it's their own responsability. |
JGreene |
Jun 4 2018, 03:20 PM
Post
#4
|
Group: Members Posts: 4 Joined: 4-June 18 Member No.: 26,653 |
[quote name='Christian J' date='Jun 4 2018, 12:39 PM' post='135861']
[quote name='JGreene' post='135858' date='Jun 4 2018, 09:16 PM'] On the prod side the default is 7 and on the test the default is Edge. [/quote] Could it be that the production site server sends a X-UA-Compatibility directive to force IE7 rendering? This can be done both with META tags and a HTTP header, see https://msdn.microsoft.com/en-us/library/ff...5(v=vs.85).aspx Glad you did post this because I added a meta tag for IE=EDGE to the html, put the url in the Compatibility list and my page works like a charm along with the underneath php. Thank you so much. |
Lo-Fi Version | Time is now: 26th April 2024 - 04:02 AM |