Forum Discussion
Cason_McGowan_1
Nimbostratus
NimbostratusAlways proxy issue
I'm trying to set up WA to do compression only for a site, no caching. I'm having a problem with the "Always proxy requests" proxy option, in that when it's enabled, the response to the client has always set "Cache-control: no cache". I have the Client Cache set to "Do not change", however it doesn't seem to have any affect. In theory, it should just be passing through what it receives from the origin web server, but in practice "no cache" is being set on every response back to the client. I have a WA 4500, running 9.4.7. Has anyone else experienced this?
rb1980_75708In short, yes. There are a lot of "issues" involving the "do not change" option.
It depends on if you want just WA to not cache it, or if you still want caching on the client.
If you want no caching at all, take off the always proxy, then set the WA cache and Client Cache all to "0 Seconds" under the Lifetime rules in the policy. If you want client caching, configure a max-age under the client section, but leave WA on 0.
I think that'll work...
Cason_McGowan_1Thanks for your response... I did not want caching, & previously I had set always proxy off & Lifetime cache to 0 seconds like you suggested. This seemed to work OK for a while, but then I got a report that the WA was serving up stale cache data, so I started looking at the always proxy option again. I contacted F5 support, and the problem I was having with always proxy turned out to be a known issue... they provided a workaround that fixed my problem.- rb1980_75708Can you elaborate on the workaround? Always good to share in case others have the same problem.
- Cason_McGowan_1Yes, it now has it's own Solution Id, check out SOL10318 on support.f5.com