> On Wed, 24 Mar 2004, Matus UHLAR - fantomas wrote:
> > I am tracing a problem with forwarding loop. I tried to tune debugging to
> > get client IP in cache_log, however I was unable to find which section set
> > up to which level in debug_options.
> >
> > looking at the sources It seems that this could not be done in 2.5stable4.
> > am I right? Should I fill up a bug report to ask for this?
On 24.03 10:40, Henrik Nordstrom wrote:
> Or better yet, make a patch and file that with the bug report. It would be
> good to have the client IP in cache.log next to the rejected request
> details (applies both to forwarding loops and invalid requests).
filled as bug 948, however I probably won't be able to make a patch, at
least not in short time :(
> But as Marc said, it is not difficult to identify the client IP by looking
> in access.log for what happened at the same time, and for forwarding loops
> there is a great deal of information already in the HTTP headers logged in
> cache.log, including a full trace of how the request has been forwarded
> (see the Via and X-Forwarded-For headers)
Well, the HTTP headers in some cases include something that is not 100%
usefull for me.
however, thanks for help
-- Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. "Two words: Windows survives." - Craig Mundie, Microsoft senior strategist "So does syphillis. Good thing we have penicillin." - Matthew AltonReceived on Wed Mar 24 2004 - 04:06:31 MST
This archive was generated by hypermail pre-2.1.9 : Thu Apr 01 2004 - 12:00:02 MST