Hey There,
I was wondering about this setup you do have there.
I do not know of any bugs that would not allow you to set explicitly
"Cache-control" in IIS 7+.
Since I am not working at MS I am not sure I can even try to resolve the
issue but I have seen this issue in the past while there is a usage of
explicit "cookies" per each session on the server even if it's not needed.
It's like my browser is a very nice guy that "accepts" all cookies by
default and there for everybody use them.
For example a session ID cookie is not needed and needs to be explicitly
disabled by default on all static content..
If you do have any relation to this website in an administrative way
there are ways to solve these issues using an IIS expert consulting.
In a case that there is a usage of ignore-private you should consider
identifying what resources you need to explicitly force this directive
on to make sure no private content will be exposed to anyone who is not
permitted to watch it.
Eliezer
On 22/11/13 12:02, Lê Trung Kiên wrote:
It seems that IIS7.5 has bugs that cannot change "Cache-control: private"
header.
However Squid 3.1 deals with this by using "ignore-private", squid 3.2 or
3.3 doesn't work with this directive.
Any suggest solutions please?
