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 guy
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
Dear Yuri,
MR Amos is sure !!
we will see a solution Dear Amos ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674378.html
Sent from the Squid - Users mailing list archive at Nabble.com.
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
04.11.15 21:59, Amos Jeffries пишет:
> On 5/11/2015 3:26 a.m., joe wrote:
>> if you notice not only dynamic static img as well
>>
>
> Yeah, and hits and misses. Basically all possible processing codes are
> replaced with "SWAPFAI_MISS".
>
>
On 5/11/2015 3:26 a.m., joe wrote:
> if you notice not only dynamic static img as well
>
Yeah, and hits and misses. Basically all possible processing codes are
replaced with "SWAPFAI_MISS".
Though I do notice that the other log entries are showing things that
could not possibly happen on a
if you notice not only dynamic static img as well
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674371.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
those ar enough i gess i dont wana flud the forum lol and they ar alot
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674370.html
Sent from the Squid - Users mailing list archive at Nabble.com.
__
>>I've been trying to figure out how it happens for the last year or so.
>>Apparently everybody (all three of you...) but not me can see it
happening.
>>The proxies I manage do not have it happen, and I can't seem to force it
>>to happen either unless I unmount or delete the HDD cache directories
1436416269.376343 10.3.2.15 TCP_SWAPFAIL_MISS/304 373 GET
http://xch.directrev.com/js/gb.min.js?s=S0003066 - DIRECT/xch.directrev.com
application/x-javascript
1436416269.376354 10.3.2.15 TCP_SWAPFAIL_MISS/304 373 GET
http://xch.directrev.com/js/gb.min.js?s=S0004215 - DIRECT/xch.directrev.co
On 4/11/2015 11:51 p.m., joe wrote:
>> I don't think the two are the same at all.
> right they ar 2 diferent problem and they ar very bad for production to be
> on
>
>> REFRESH is (in jo's case) an indicator that the private content is being
>> checked before use. If the server behaves itself th
translate to browser act like
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674365.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users mailing list
Loool Joe, really are you going back to V2.7 ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674362.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-us
You are right Yuri,
its like a proxy bypassed system ..
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674361.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
04.11.15 17:05, Amos Jeffries пишет:
> On 4/11/2015 11:35 p.m., HackXBack wrote:
>> and how we can cache Control:private content ?
>> must be a choice ?
>
> Yes. By adding the ignore-private refresh_pattern control.
>
> Though be aware it still d
On 4/11/2015 11:35 p.m., HackXBack wrote:
> and how we can cache Control:private content ?
> must be a choice ?
Yes. By adding the ignore-private refresh_pattern control.
Though be aware it still does very bad things to data in most Squid 3.x
versions for some configs. It is only fully safe in v4
>I don't think the two are the same at all.
right they ar 2 diferent problem and they ar very bad for production to be
on
>REFRESH is (in jo's case) an indicator that the private content is being
>checked before use. If the server behaves itself the answer would be
>UNMODIFIED/304 not MODIFIED/
and how we can cache Control:private content ?
must be a choice ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-REFRESH-MODIFIED-tp4674325p4674357.html
Sent from the Squid - Users mailing list archive at Nabble.com.
_
On 4/11/2015 11:53 a.m., HackXBack wrote:
> what joe is going to tell us is that his HIT ratio decrease and he is seeing
> TCP_REFRESH_MODIFIED instead of tcp_hit when he used V4
> this problem is right also with tcp swalfail miss
I don't think the two are the same at all.
REFRESH is (in jo's ca
On 4/11/2015 11:38 a.m., joe wrote:
> at least you pay attention on "gvs" :) +1
>
> lets forget about youtube:) im just asking why TCP_REFRESH_MODIFIED if
> i don't or did not force reload
> ignore-privet its working but ignore-reload its not .. suppose to prevent
> TCP_REFRESH_MODIFIED from
what joe is going to tell us is that his HIT ratio decrease and he is seeing
TCP_REFRESH_MODIFIED instead of tcp_hit when he used V4
this problem is right also with tcp swalfail miss
with V3.4 these strange problems is not exists ..
--
View this message in context:
http://squid-web-proxy-cache
at least you pay attention on "gvs" :) +1
lets forget about youtube:) im just asking why TCP_REFRESH_MODIFIED if
i don't or did not force reload
ignore-privet its working but ignore-reload its not .. suppose to prevent
TCP_REFRESH_MODIFIED from hapening right ?
and talking about private con
On 4/11/2015 9:53 a.m., Yuri Voinov wrote:
>
> To talk was objective: show the config (squid.conf) and URL, which
> causes problems with caching. Telepaths on holiday in Bali. Personally,
> I have no idea either looks like configuration or a URL you're trying to
> cache. In such a situation it is
>You give too few info to solve your problem.
well i give a good info bro this problem its all over the internet lots of
ppl ar complaning about it
>English is not in your list, of course.
right dude im lebanise but i use to live in canada and in US my english is
mixed hehe canadian US lol
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
To talk was objective: show the config (squid.conf) and URL, which
causes problems with caching. Telepaths on holiday in Bali. Personally,
I have no idea either looks like configuration or a URL you're trying to
cache. In such a situation it is imp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
04.11.15 2:14, joe пишет:
>> Take a look onto Cache-Control header once more.
>
>> It you haven't refresh_pattern with "ignore-private" for this URL and
>> similar, it always not be cached.
>
> if this ignore-private useless then one more bug squ
>Take a look onto Cache-Control header once more.
>It you haven't refresh_pattern with "ignore-private" for this URL and
>similar, it always not be cached.
if this ignore-private useless then one more bug squid has is this wat you
telling me
>If this URL is dynamic, it also always not be cach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Because of.
Take a look onto Cache-Control header once more.
It you haven't refresh_pattern with "ignore-private" for this URL and
similar, it always not be cached.
If this URL is dynamic, it also always not be cached. Without special
solutions.
Yuri Voinov lol no its not porn its some url ppl ar daying to get it
cached dont worry about it it dose cache as i sayd befor please read ^im
not worry about it im worry about why it dose not stay in cache as i
explaned befor ^
--
View this message in context:
http://squid-web-proxy-cach
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Heh, this porn :) URL has Cache-Control: private.
And without special things will not be cached.
04.11.15 1:54, joe пишет:
> hi amos
> this is the header
> Connection: keep-alive
>
> HTTP/1.1 200 OK
> Last-Modified: Mon, 02 Nov 2015 08:13:05 GM
hi amos
this is the header
Connection: keep-alive
HTTP/1.1 200 OK
Last-Modified: Mon, 02 Nov 2015 08:13:05 GMT
Content-Type: video/mp4
Date: Tue, 03 Nov 2015 18:25:03 GMT
Expires: Tue, 03 Nov 2015 18:25:03 GMT
Cache-Control: private, max-age=21297
Accept-Ranges: bytes
Content-Length: 131072
acce
Hi jo,
Pause. Breath.
If I'm reading that long sentence right you are getting REFRESH_MODIFIED
responses from servers with "new" content to be cached, which has not
actually changed.
What URL or URLs ?
>
> as i understand squid look at
> file size
> date expiery
> +++ if the income header o
31 matches
Mail list logo
