Discussion:
[squid-users] need 206 to be 200
HackXBack
2015-01-25 04:03:51 UTC
Permalink
hello,
i have specific site is tcp_miss 206 and i need it to be 200
what is the best way to do that ?
Thanks



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/need-206-to-be-200-tp4669315.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Amos Jeffries
2015-01-25 04:36:43 UTC
Permalink
Post by HackXBack
hello,
i have specific site is tcp_miss 206 and i need it to be 200
what is the best way to do that ?
http://www.squid-cache.org/Doc/config/range_offset_limit/

Amos
HackXBack
2015-01-26 12:38:46 UTC
Permalink
I always see in access.log for the partial content
TCP_HIT_ABORTED/206
and this content eat my whole bandwidth

my conf is

range_offset_limit none partial
quick_abort_min 1840 KB
quick_abort_max 1844 KB



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/need-206-to-be-200-tp4669315p4669330.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Amos Jeffries
2015-01-26 13:01:45 UTC
Permalink
Post by HackXBack
I always see in access.log for the partial content
TCP_HIT_ABORTED/206
ABORTED means the client disconnected. There is nothing you can do about
that in Squid.

HIT means the object delivered came from cache. No upstream bandwidth
was consumed in the process.
Post by HackXBack
and this content eat my whole bandwidth
The 206 means client is fetching a range of data out of a larger object.
Turning that into a 200 (full-object) delivered to client will only
spend more bandwidth.
Post by HackXBack
my conf is
range_offset_limit none partial
quick_abort_min 1840 KB
quick_abort_max 1844 KB
These are all controlling Squid contact with servers. Limiting upstream
bandwidth expenditure when the client aborts. Which is useful for
TCP_MISS_ABORTED/206 cases.

Since your log says HIT, the only thing you could do in Squid is
completely reject these clients requests.

Amos

Loading...