Unfortunately, changing Compatibility View Settings in our corporate environment is not possible due to restrictions and some other issues.
I have tried going the route of adding the header from within the container:
added add_header “X-UA-Compatible” “IE=Edge”; in /etc/nginx/conf.d/discourse.conf below “server {”
and restarted nginx (service nginx stop; service nginx start;)
as well as added “<meta http-equiv=“X-UA-Compatible” content=“IE=Edge,chrome=1” />” via Customize → Edit CSS/HTML.
The first workaround added the header in a v1.8.x Discourse deployment, but same thing done in a v1.9.x deployment does not work. I checked the headers with Fiddler and the additional header is not in there with v1.9. The additional meta-tag is indeed in, but does not “switch off” compatibility mode, maybe because it is too far below and not the first meta entry.
Tried a complete rebuild and then changing the dicourse.conf again, too - just to exclude that I messed up something - same effect.
I am trying to get v1.9.x working with IE11 in the local network since a while now and am a bit lost I have to admit. I have opened a topic some while ago, too, and have been asked to continue here: https://meta.discourse.org/t/ie11-in-compatibility-mode-intranet-is-getting-your-browser-is-too-old/66185
Is there anything I’ve missed in terms of changes made to the nginx-setup within the container in v1.9? Do I need to set the header elsewhere, too?
Thanks a lot in advance and cheers
Thomas