> > > 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)
> On Wed, 24 Mar 2004, Matus UHLAR - fantomas wrote: > > Well, the HTTP headers in some cases include something that is not 100% > > usefull for me. On 24.03 17:10, Henrik Nordstrom wrote: > Then extending the information with the client IP is most likely also not > going to be 100% useful for you.. the client IP here is the IP address of > the peer who sent us the request, and this you SHOULD be able to derive > from the Via header or you have a very strange and unreliable peering > setup.. The Via header contains a hostname, which is not very reliable in this case... -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; 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. One OS to rule them all, One OS to find them, One OS to bring them all and into darkness bind them
