[squid-users] TCP_REFRESH_MODIFIED
Amos Jeffries
squid3 at treenet.co.nz
Thu Nov 5 12:38:26 UTC 2015
On 5/11/2015 10:54 p.m., joe wrote:
> HI Amos after diging and testing wat i found for you is ....
> TCP_REFRESH_MODIFIED/200 && TCP_SWAPFAIL_MISS/200 ar connected
>
> i will try to explain how dose that happen hoop that im clear enough for you
> to understand
>
>
> ok lets say the way you guys mod the code for the TCP_REFRESH_MODIFIED wen
> the file expierd or squid think its modified it delete it right or force
> newer copy so wat happen here squid thing its swap fail sending wrong flag
> TCP_SWAPFAIL_MISS and it should be TCP_REFRESH_MODIFIED
>
> so dont dig as you say for wrong idea its just in the log or what ever
> its just wrong flag that happen wen it suppose to be TCP_REFRESH_MODIFIED
>
> that after i spend 24 hr digging to re produce that error
>
Thank you for looking into it. Where in the code is the flag being sent
wrong?
Would you care to provide a patch that fixes it or at least enough
information for someone else to do so?
> and pls put back as it was before the USE_HTTP_VIOLATIONS and allow us to
> decide if that object we need to have it stay longer in cache and re mod
> TCP_REFRESH_MODIFIED to have control making the object stay as before that
> will correct the issu
>
Let me ask you:
What do you think "ignore-must-revalidate" did?
What do you think "ignore-auth" did?
What do you think "ignore-auth ignore-must-revalidate" did?
What do you think "ignore-private" does?
What do you think "ignore-private ignore-must-revalidate" did?
I will predict right now before you answer that your answer is going to
be wrong. Hint: the documentation was incomplete and since squid-3.1 has
not been correct.
Amos
More information about the squid-users
mailing list