WA behaving differnt depending on VS

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.