For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

keith_varga_107's avatar
keith_varga_107
Icon for Nimbostratus rankNimbostratus
Nov 01, 2013

New version of Chrome, and URL hangs through the F5

Hi DevCentral Team,

 

We have an interesting low priority anomaly on one of our web servers going through the F5 load balancer. We're running 10.2.3 build 123 HF1 (32bit) physical LB pair.

 

(1) load the new version of google chrome Version 30.0.1599.101 m.

 

(2) Leave the chrome browser open for the following steps: (3) load https://productionstaging.fierydashboard.com/ . (4) it should work ok.

 

(5) clear your temp internet files in chrome: (CTRL-Shift-Del), then press Enter. (6) load https://productionstaging.fierydashboard.com/ . (7) this is the problem, it just hangs forever... (8) nothing is showing up in the weblogs on the app server when it hangs at this point.

 

(9) the same steps work fine in IE and firefox. (10) If we bypass the load balancer, and load the server directly, then it works ok in the latest chrome too. (11) we are hitting a virtual server on the F5 with only 1 enabled node in the pool behind it; we disabled the other node for testing.

 

thanks much, Keith

 

4 Replies

  • keith_varga_107's avatar
    keith_varga_107
    Icon for Nimbostratus rankNimbostratus
    Nov 02, 2013
    Team, More information on this one. It seems if you hardcode you hosts file to a shorter dns name, that the above test works in chrome through the load balancer. hosts entry: 216.151.85.217 ps.fierydashboard.com Then try the steps using the shorter 2 character dns name, and chrome works through the load balancer: https://ps.fierydashboard.com/FDB/ADB/ADBLogin.aspx So, maybe that is a clue. We were able to go up to 6 characters, and then it starts breaking at the 7th.
  • IheartF5_45022's avatar
    IheartF5_45022
    Icon for Nacreous rankNacreous
    Nov 04, 2013

    Apparently there is a bug in the 10.2.3 firmware that causes it to hang when a client sends a Client Hello larger than 255 bytes, and I can confirm that when we access your site on the new Chrome you are using a Client Hello of less than 255 bytes but when I go to re-load it jumps up to 263 (for me anyway).

     

    Here is some more info; https://code.google.com/p/chromium/issues/detail?id=303398

     

    Also I can confirm that we are running 10.2.4 on our websites and do not have the issue, so even though the release notes for 10.2.4 do not specifically address THIS issue, it may fix it.