On 09/11/10 03:08, donovan jeffrey j wrote:
On Nov 5, 2010, at 7:37 PM, Amos Jeffries wrote:
On 06/11/10 03:28, donovan jeffrey j wrote:
On Nov 5, 2010, at 10:24 AM, Amos Jeffries wrote:
On 06/11/10 03:20, donovan jeffrey j wrote:
<snip>
does this look right ?
#redirect_program /usr/local/bin/squidGuard -c
/usr/local/squidGuard/squidGuard.conf
url_rewrite_program /usr/local/bin/squidGuard -c
/usr/local/squidGuard/squidGuard.conf
#redirect_children 100
url_rewrite_children 100
Yes.
is it okay to issue a - k reconfigure for this change or it better to wait
until not many users are accessing?
-j
reconfigure is enough. It is just a cosmetic config change at this point.
Amos
okay im getting same message under load.
2010/11/08 09:04:50| client_side_request.cc(1047) clientRedirectDone:
redirecting body_pipe 0x2135be20*2 from request 0x14e14200 to 0x8ac0200
2010/11/08 09:04:56| client_side_request.cc(1047) clientRedirectDone:
redirecting body_pipe 0x1fabb330*2 from request 0xc7a5e00 to 0xe05d000
2010/11/08 09:05:00| client_side_request.cc(1047) clientRedirectDone:
redirecting body_pipe 0x2135be20*1 from request 0x8fa7200 to 0x127f7400
2010/11/08 09:05:06| client_side_request.cc(1047) clientRedirectDone:
redirecting body_pipe 0x20606560*1 from request 0x11508200 to 0x11add800
2010/11/08 09:05:07| client_side_request.cc(1047) clientRedirectDone:
redirecting body_pipe 0x21278360*1 from request 0xbcbc00 to 0x190d4a00
and yes there is redirection going on so it's not lying to me. ^^^^^^^^^^^
client redirect done. is this just a notification of the redirect ? or is it an
error ?
It's a notice that the redirect changed something potentially dodgy.
I've canvased the dev who might know better than me and have not come up
with any reason to keep it.
It may be worth adding "url_rewrite_access deny CONNECT" if possible
to protect against tunnel problems. Beyond that it can be ignored or
patched out of existence.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.9
Beta testers wanted for 3.2.0.2
