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

Ferg_104721's avatar
Ferg_104721
Icon for Nimbostratus rankNimbostratus
Sep 29, 2011

WA behaving differnt depending on VS

Hi All     I am currently having an issue with WA returning 304 for specific content when moved to another VS. My architecture [see diagram below] is normally that WA is applied on a "Front End"...
application delivery
performance
wa
Johnny_Schmidt_'s avatar
Johnny_Schmidt_
Historic F5 Account
Dec 29, 2011
WA is going to serve up a 304 for content which is requested with a conditional GET and for which it's cache is valid (either the cache hasn't expired or a conditional request to the OWS returned a 304). Double check your header values for the conditions (If-Modified-Since, etc) to shed light on who is making what decision about when to serve a 304. The S code in the pvinfo header ought to also help figure out who sent the original 304.

 

 

 

Hopefully that gets you to the right place. You may want to disable RAMCACHE in this situation, making sure it's off on both VS's that the WAM traffic foes through.