I have a HA pair of 3900's running v10.2.3 LTM and ASM, with a blocking
policy in place on one of my production VS/applications. We also use
OneConnect, the WAN optimised TCP profile and the WAN optimised HTTP profile on
this virtual server.
From testing it appears that the HTTP class with application security
enabled that we've applied to this virtual server is blocking both desktop and
mobile browsers from accessing our homepage. Well, I say blocking but the
client doesn't get a block page, just a blank page. FYI the class was created
Using Firefox and Fiddler I can see that the client receives a 504
response (gateway timeout?) and gives up. What is strange is that if the same
client hits a URL deeper in the site from a Google link then they can load the
We have a second VS going to a backup/pre-prod group of servers that run
exactly the same application code as the production servers. If I apply all the
same iRules, TCP settings etc then cookie-less clients can access the site,
it's only when I apply that same HTTP class that it breaks again.
I'm not an ASM (or LTM!) superstar so can someone help point me in the
right direction, please? I'm guessing there's a tick box somewhere...