You did supply the correct meta tags. The problem is that those tags have to be first, or ie will start processing with the older engine and ignore them. Throwing them in the http response header guarantees the page to be handled by the non-ie7 rendering engine. It is somewhere in the IE support spec that this is actually a proper way to do this. I'll have to dig up the document.
> On Sep 13, 2014, at 2:40, Maxim Solodovnik <[email protected]> wrote: > > Maybe we can set some IE specific META? I can add it to the page if you can > tell me with META should be added > >> On 13 September 2014 01:39, William Overstreet >> <[email protected]> wrote: >> Well, turns out that if compatibility view is enabled, and the first thing >> through isn't the webs server telling the browser to use the latest and >> greatest, the browser falls back to IE7 compatibility, which does not work. >> I'm using urlrewritefilter-4.0.3.jar to make the internal tomcat web server >> send the headers to force IE to use the latest. >> >> ${RED5_HOME}/webapps/openmeetings/WEB-INF/lib/urlrewritefilter-4.0.3.jar >> ${RED5_HOME}/webapps/openmeetings/WEB-INF/web.xml >> ${RED5_HOME}/webapps/openmeetings/WEB-INF/urlrewrite.xml >> >> # diff web.xml web-old.xml >> 37,48d36 >> < <filter> >> < <filter-name>UrlRewriteFilter</filter-name> >> < >> <filter-class>org.tuckey.web.filters.urlrewrite.UrlRewriteFilter</filter-class> >> < </filter> >> < >> < <filter-mapping> >> < <filter-name>UrlRewriteFilter</filter-name> >> < <url-pattern>/*</url-pattern> >> < <dispatcher>REQUEST</dispatcher> >> < <dispatcher>FORWARD</dispatcher> >> < </filter-mapping> >> < >> >> # cat urlrewrite.xml >> <?xml version="1.0" encoding="utf-8"?> >> <!DOCTYPE urlrewrite PUBLIC "-//tuckey.org//DTD UrlRewrite 4.0//EN" >> "http://www.tuckey.org/res/dtds/urlrewrite4.0.dtd";> >> >> <urlrewrite> >> >> <rule> >> <condition >> type="request-uri">^(/openmeetings/wicket.*)$</condition> >> <condition name="user-agent">.*MSIE.*</condition> >> <set type="response-header" >> name="X-UA-Compatible">IE=Edge</set> >> </rule> >> <rule> >> <condition >> type="request-uri">^(/openmeetings/swf.*)$</condition> >> <condition name="user-agent">.*MSIE.*</condition> >> <set type="response-header" >> name="X-UA-Compatible">IE=Edge</set> >> </rule> >> <rule> >> <condition type="request-uri">^(/openmeetings/)$</condition> >> <condition name="user-agent">.*MSIE.*</condition> >> <set type="response-header" >> name="X-UA-Compatible">IE=Edge</set> >> </rule> >> <rule> >> <condition >> type="request-uri">^(/openmeetings/screen.upload.*)$</condition> >> <condition name="user-agent">.*MSIE.*</condition> >> <set type="response-header" >> name="Cache-Control">max-age=5</set> >> </rule> >> </urlrewrite> >> >> >> >>> On Thu, Sep 11, 2014 at 11:17 AM, William Overstreet >>> <[email protected]> wrote: >>> Thanks for that, was getting nailed with the Compatibility view. For some >>> reason corp says we need it turned on reasons. I guess I can edit the pages >>> to present the correct html to force non-compatibility view. >>> >>> >>>> On Wed, Sep 10, 2014 at 10:42 PM, Maxim Solodovnik <[email protected]> >>>> wrote: >>>> can you check IE without proxy? >>>> can you check JS console in IE (F12 if I'm not mistaken) >>>> It seems jquery and/or some CSS files were not loaded (maybe because of >>>> proxy) >>>> >>>>> On 11 September 2014 00:27, William Overstreet >>>>> <[email protected]> wrote: >>>>> Trying to use openmeetings internally on our lan. I'm running into the >>>>> issue of only internet explorer is refusing work. all the other browsers >>>>> have no issues, reguardless of the OS. The login screen looks normal, >>>>> post login looks like http://i.imgur.com/nwhGX88.png , and if I try to >>>>> join straight to a meeting, all I get is that swirling icon in the middle >>>>> of the screen, the one before the loading bar appears. >>>>> >>>>> The network is stuck behind a http proxy. >>>> >>>> >>>> >>>> -- >>>> WBR >>>> Maxim aka solomax > > > > -- > WBR > Maxim aka solomax
