You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
This morning some of our customers told us they can not reach our website. We realized that only customers with windows systems contacted us. After some research we found out that annotation nginx.ingress.kubernetes.io/force-ssl-redirect: "true" uses a 308 rewrite. Which is the best way to rewrite but sadly it does not support all clients. Old Internet Explorer versions have problems with it (for example win 7). We could fix it ourselves quickly through:
Configmap: http-redirect-code: "301"
What you expected to happen:
I would expect to use 301 as default after this incidence. I bet there are more companies out there which will fall into this trap. 308 is faster but it is saver to use 301.
So basically i would suggest that i make a pr to change default rewrite to 301. Change documentations that we use 301 because of internet explorer. I would keep the text about 308 and tell our users that it makes sense to use 308 if ie is unimportant.
What are you opinions about that?
Greetings, Thomas
The text was updated successfully, but these errors were encountered:
Ingress Controller 0.10.2
Kubernetes 1.8.x
What happened:
This morning some of our customers told us they can not reach our website. We realized that only customers with windows systems contacted us. After some research we found out that annotation
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
uses a 308 rewrite. Which is the best way to rewrite but sadly it does not support all clients. Old Internet Explorer versions have problems with it (for example win 7). We could fix it ourselves quickly through:Configmap:
http-redirect-code: "301"
What you expected to happen:
I would expect to use 301 as default after this incidence. I bet there are more companies out there which will fall into this trap. 308 is faster but it is saver to use 301.
How to reproduce it
Create a ingress rule with
nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
annotation and visit the website via http on an internet explorer.https://www.browserling.com/browse/win/vista/ie/9/$YOURDOMAIN
So basically i would suggest that i make a pr to change default rewrite to 301. Change documentations that we use 301 because of internet explorer. I would keep the text about 308 and tell our users that it makes sense to use 308 if ie is unimportant.
What are you opinions about that?
Greetings, Thomas
The text was updated successfully, but these errors were encountered: