-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permanent redirect 308 not supported in IE11 #1825
Comments
@tlbdk it's hard to define defaults. We could "complain" about the TLS ciphers too because they not work with java 6 so you need to adjust the configuration using the configmap.
We are not going to start doing this. The template is already too complex and adding if sections is not a solution.
Can you be more specific or show an example? http://test.greenbytes.de/tech/tc/httpredirects/ |
@aledbf older and unsupported versions of IE and Java should die as quickly as possible. But IE 11 i guess we have to live with a bit longer as we still have quite a few users on it and it's still supported. Might have been nice to have kept 301 as default and 308 as the option, but hey other people will find this issue and apply the same fix as us. We did not notice the issue because of HSTS, so if we ever visited the site before with the old 301 default the browser would remember to do the automatic redirect to https and skip the new 308 page. Only new customers would get this lovely page: I did not have time to debug this, but from past experience, IE has some funny ways to find out if it should render a page in comparability mode and this might also affect if it supports 308. This could mean that one fix could be to set the special IE meta tags/headers that tells it not to run in comparability mode or make the redirect page's HTML look more modern so comparability mode won't kick in. |
It's hard to define default that will work for all the users. |
Closing. Please adjust the redirect code to 301. Keep in mind doing this you cannot do redirects with post request. |
Ingress Controller 0.10.2 What happened: What you expected to happen: How to reproduce it So basically i would suggest that i change documentations that people should use 301 because of internet explorer. Greetings, Thomas |
can Annotation |
The "308 Permanent Redirect" HTTP status code is not supported in Internet Explorer before Windows 10. This patch sets the http->https redirect to use the "301 Moved Permanently" status code instead. See: * https://rt.uninett.no/Ticket/Display.html?id=174013#txn-2526684 * https://rt.uninett.no/Ticket/Display.html?id=174983#txn-2542259 * kubernetes/ingress-nginx#1825 * https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#http-redirect-code
I tried the redirect fix from @thomaspeitz but this time I get a "This page can’t be displayed" error. I summarised the question in this stackoverflow question. Any help or pointing in the right direction would be much appreciated as I am stuck with how to debug this further. |
IE 11 does not support permanent redirect 308 with default headers, so it might not be the best default.
It was introduced in this pull request:
#1776
You could also support a fall back mode based on user agent:
https://stackoverflow.com/questions/37701100/redirecting-ie-7-and-ie-11-by-useragent-nginx-config
It might be possible to get IE 11 to support permanent redirect 308 if the redirect page presented does not trigger compatibility mode, but older versions of IE still won't support 308.
The text was updated successfully, but these errors were encountered: