Forum Discussion

Iceman_25111's avatar
Iceman_25111
Icon for Nimbostratus rankNimbostratus
Sep 19, 2013

Forcing to IE 9 Compatability mode iRule

Still sorta new to iRules and I am wondering if anyone can validate this simple iRule I wrote? Hopefully I am on the right track here.

 

What the app teams are ultimately trying to accomplish is to force IE 10 into IE9 compatibility mode. So what I was going to do with the F5 is for every HTTP Response back from the F5 I would insert into the response HTTP header file the following, so the top of the response http header file would look the following:

 

 

Would by all accounts, would this iRule I wrote do it as I hoped it will. I have not been able to really test it yet, because I will have place in semi-production system, so I want to have you review it first to get your thoughts.

 

when HTTP_RESPONSE { HTTP::header insert }

 

6 Replies

  • Hi Iceman, this code needs to be inserted into the http payload.

     

    An http header (as in your sample iRule) would be the wrong place.

     

    As it needs to placed between the tags (just googled it), your iRule will not work.

     

    I can have a look at it tomorrow night, if there is no solution in the meantime. Stephan

     

  • If you still need it in the head section, you could use a STREAM profile and the something like the following:

    when HTTP_REQUEST {
        STREAM::disable
        HTTP::header remove "Accept-Encoding"
    }
    when HTTP_RESPONSE {
        if {[HTTP::header value Content-Type] contains "text"}{
            STREAM::expression {@@@}
            STREAM::enable
        }
    }
    
  • I just set up a new Citrix instance on my BIG-IP and encountered the exact same issue when using IE11. I added the iRule defined by 'What Lies Beneath' and it works perfectly.

     

  • Can someone confirm ? we need to do SSL offload to modify the HTTP the header right ?

     

    • Baddogsettle_16's avatar
      Baddogsettle_16
      Icon for Nimbostratus rankNimbostratus
      I recently replaced our Citrix Secure Gateways with F5 LTM/APM/ASM. Initially had compatibility issues, but added the iRule from 'What lies beneath' and it worked great.