Re: [squid-users] 000 status code being logged for redirects

2003-12-18 Thread Henrik Nordstrom
On Thu, 18 Dec 2003, Jesse Reynolds wrote:

 We have an array of squid servers acting as reverse proxy servers 
 (web accelerators). They also work as URL rewriters, via the 
 redirector interface, eg bouncing http to https in some cases, and 
 mapping certain paths to different backend web servers...

Which Squid version?

If this is 2.5.STABLE4 please file a bug report. Otherwise first try 
upgrading.

Regards
Henrik



Re: [squid-users] 000 status code being logged for redirects

2003-12-18 Thread Jesse Reynolds
At 8:23 +0100 18/12/03, Henrik Nordstrom wrote:
On Thu, 18 Dec 2003, Jesse Reynolds wrote:

 We have an array of squid servers acting as reverse proxy servers
 (web accelerators). They also work as URL rewriters, via the
 redirector interface, eg bouncing http to https in some cases, and
 mapping certain paths to different backend web servers...
Which Squid version?

If this is 2.5.STABLE4 please file a bug report. Otherwise first try
upgrading.
Yes it's 2.5.STABLE4, sorry to forget to mention that!

OK, I'll file a bug. :-) For now I'm filtering my log files to 
replace the 000's with 302's, which works for now, kludgey as it is.

Cheers

Jesse

--

  ::: Jesse Reynolds +61 (0)414 669 790 ::: AIM - jessedreynolds :::
  ::: Virtual Artists Pty Ltd, Adelaide ::: http://www.va.com.au :::


[squid-users] 000 status code being logged for redirects

2003-12-17 Thread Jesse Reynolds
Hello

We have an array of squid servers acting as reverse proxy servers 
(web accelerators). They also work as URL rewriters, via the 
redirector interface, eg bouncing http to https in some cases, and 
mapping certain paths to different backend web servers...

I am getting lots of lines in my access.log files with 000 for the 
HTTP status code. It looks like it's logging this when it serves a 
redirect. Here are some example lines (as identified by analog which 
considers the lines corrupt on account of the 000 status code:)

Wed Dec 17 23:29:05 2003161 203.45.116.35 TCP_MISS/000 0 GET 
http://mydomain.dom:443/act/ho/home.xml - DIRECT/163.241.210.3 -
Wed Dec 17 23:29:08 2003 22 203.45.116.35 TCP_MISS/000 0 GET 
http://mydomain.dom:443/act/ho/home.xml - DIRECT/163.241.210.3 -
Wed Dec 17 23:31:22 2003  6 203.12.97.112 TCP_MISS/000 220 GET 
http://www.mydomain.dom/ - NONE/- -
Wed Dec 17 23:31:23 2003 30 202.158.104.38 TCP_MISS/000 245 GET 
http://mydomain.dom/stu/dummy.html - NONE/- -
Wed Dec 17 23:32:29 2003  0 211.108.90.39 TCP_MISS/000 245 GET 
http://mydomain.dom/stu/dummy.html - NONE/- -

the first and second lines are the web server issueing a redirect, 
the rest of them are the redirector script telling squid to issue a 
redirect to https.

Is this supposed to happen? Any way around it so that I can get our 
log analysis software to read these lines?

Thanks
jesse
--

  ::: Jesse Reynolds +61 (0)414 669 790 ::: AIM - jessedreynolds :::
  ::: Virtual Artists Pty Ltd, Adelaide ::: http://www.va.com.au :::