Forum Discussion

rob_miller_7792's avatar
rob_miller_7792
Icon for Nimbostratus rankNimbostratus
May 08, 2007

simple iRule failing with IE 7.0

The search feature didn't return anything for this.

 

 

We are on Big-IP Kernal 4.5.12 Build 19-a

 

 

For some time now we have experienced problems with customers hanging on our website. All of the customer's on IE7.0. After much testing, we have determined the problem is with our iRule for the site.

 

 

This rule simply kicks out certain requests. If I remove all of the conditions but 1 from the iRule, then IE7.0 appears to work fine. However, whenever I put 2 or more of the conditions in, then the browser will occassionally hang for 6 or 7 minutes before returning the response. Our web servers do not receive the hit until after the 6 or 7 minutes has expired, and then we serve up the page as normal.

 

 

Here is the rule:

 

 

if (http_header("User-Agent") matches_regex "wget" or client_addr == 213.130.53.94 or http_uri contains "txtLastName" or client_addr == 66.153.64.218 or http_uri contains "images2002" or http_uri contains "favicon.ico" or http_uri contains "owssvr.dll" or http_uri contains "cltreq.asp" or http_uri contains "globalconfig") {

 

discard

 

}

 

else {

 

use pool eMozartNet_http

 

}

 

 

 

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    That sounds like you might be encountering a bug. Or perhaps IE7 is sending requests in a way that BIG-IP isn't handling correctly. Either way, you could probably contact support for help isolating the cause of the issue as it appears there might be a bug.

     

     

    Does every request always hang when using IE7? Can you make identical requests in IE6 without encountering the failure? Can you mix and match the conditional checks you're performing in the rule to find out if it's one particular test that is causing the hang? Maybe try creating a test virtual server and use a rule with just one of the tests at a time. If you can't repro the issue, then try adding in more checks to see when it starts to fail.

     

     

    Support would probably want to see tcpdumps on each VLAN the traffic is passing over to see if it is in fact the BIG-IP that's breaking the connections.

     

     

    A couple of minor suggestions on improving the rule:

     

     

    It doesn't look like you need to be using matches_regex to see if the user-agent contains the string "wget". You can use 'contains' for a more efficient test.

     

     

    Also, you could add all of the URI comparisons to a class and then use "one of" to perform the comparisons. Click here for an example of using a class.

     

     

    Aaron
  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account

    Posted By hoolio on 05/08/2007 12:02 PM

     

     

    Support would probably want to see tcpdumps on each VLAN the traffic is passing over to see if it is in fact the BIG-IP that's breaking the connections.

     

     

     

     

    hoolio makes an excellent point: Since Support is dedicated to fixing what's broken, you will need to provide Support with direct evidence of the problem you describe as a BIG-IP-created problem to make any headway on your case. Packet traces demonstrating the connections that work v. those that fail would be very helpful to that end.

     

     

    jm2c

     

    /deb