Re: [squid-users] Squid 2.7 access log and url_rewrite_program

+1 - both cases are useful.

On 10/07/2008, at 1:15 AM, Chris Woodfield wrote:

> Bug filed, #2406.
>
> As I annotated in the bug report, this behavior does have its uses,
> but not having access to the URL pre-rewrite is clearly broken
> behavior IMO. My idea solution would restore 2.6's behavior, but
> also add a logformat code to log the URL post-rewrite in addition to
> pre-rewrite if desired. If no rewriter is configured, this element
> would print null.
>
> -C
>
> On Jul 8, 2008, at 6:36 PM, Henrik Nordstrom wrote:
>
>> On tis, 2008-07-08 at 16:47 -0400, Chris Woodfield wrote:
>>
>>> I've noticed that squid 2.7STABLE3 logs incoming URLs differently
>>> than
>>> 2.6 did when using a url_rewrite_program. It appears that under 2.6,
>>> the URL logged was pre-rewrite, under 2.7 it's the URL returned by
>>> the
>>> rewriter. This presents problems as I have the potential for a large
>>> number of incoming URL hostnames being rewritten to the same origin
>>> hostname, and with the current 2.7 logging I can't tell what the
>>> incoming hostnames were.
>>>
>>> Was this an expected change? If so, can I have the old behavior
>>> back? :)
>>
>> Not expected, but now that I read the change log again it's obvious..
>>
>> File a bug so we have some place to keep a lasing discussion about
>> this.
>> Not sure today what the solution will look like.
>>
>> http://bugs.squid-cache.org/
>>
>> Regards
>> Henrik
>

--
Mark Nottingham       mnot_at_yahoo-inc.com