If I set up WAF for HTTPS I get really por performance if I want to access a Communicator Web Access Page on an IIS.
There are a lot of
method="GET" statuscode="304"
in the live log.
Could it be that the WAF has some problems with these responses if multiple clients access the pages?
If I understand the 304 right, the client should load the cached document because it has not changed since the last get.
Is it possible that a client gets the answear to load the document from the cache even if an other client loaded the document the last time?
