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

JN_42992's avatar
JN_42992
Icon for Nimbostratus rankNimbostratus
May 27, 2010

http response not always fired

Hi, I have the iRule below deployed on a chassis running 9.3.1 (latest HF). This iRule does not always work. In fact, after some debugging, I noticed that HTTP_RESPONSE is not always fired. Any idea ...
application delivery
dev
devops
iRules
JN_42992's avatar
JN_42992
Icon for Nimbostratus rankNimbostratus
May 27, 2010
Thanks Aaron for the reply. I will keep the ramcache tips in mind for a different unit I have.

 

 

For this particular unit, there is no ramcache enabled.

 

 

The server is always sending a response to the browser (HTTP 200). There is no other proxy or caching appliance deployed. There is no other iRule.

 

 

From the client perspective, HTTP_RESPONSE would be fired for 4 or 5 files in a folder for example. Let's say /css/ contains cacheable content. The Irule should be fired and the HTTP headers should be set accordingly.

 

The client would see:

 

- /css/file1.css with the correct HTTP headers

 

- /css/file2.css with the correct HTTP headers

 

- /css/file3.css with the correct HTTP headers

 

- /css/file4.css without the correct HTTP headers. It has the original from the server.

 

- /css/file5.css with the correct HTTP headers