Broken logs in transparent mode

[a...@test123.ru]

Hello,

I report this problem 3rd time and would like to get clear answer. Devs, do you confirm the bug? Are you going to fix this? Naturally, it looks like 2.1.7 "stable" will not fix logs.

>> On 01/18/2011 01:42 AM, a@test123.ru wrote:
>> I installed 2.1.5 and there is same problem with log - wrong URL.
>> # /opt/traffic/bin/traffic_logcat  /opt/traffic/var/log/trafficserver/squid.blog
>> 1295338766.964 310 192.168.1.18 TCP_MISS/200 23958 GET http:///db/msg/1249162 -
>> DIRECT/www.astronet.ru text/html -
>> 1295338767.133 132 192.168.1.18 TCP_MISS/301 410 GET http:///cycounter?www.astronet.ru -
>> DIRECT/www.yandex.ru text/html -
>> ...
>> On Wed, 19 Jan 2011 21:52:11 -0700, Leif Hedstrom <zw...@apache.org> wrote:
>> Weird, I can't see to reproduce this, in forward proxy mode ('curl -x 
>> localhost:8080 http://www.ogre.com/') I see this in my log:
>> 
>> 1295498905. 109 127.0.0.1 TCP_REFRESH_HIT/200 31647 GET 
>> http://www.ogre.com/ - DIRECT/www.ogre.com text/html -
>> 
>> On 01/20/2011 02:44 AM, a@test123.ru wrote:
>> Well, I checked explicit proxy mode - log is OK. 2.1.5 fixed that. Try to reproduce in
>> transparent mode.
>> I use iptables as follows:
>>
>> -t nat -A PREROUTING -p tcp -i eth0 --dport 80 -j REDIRECT --to-ports 3129
>> Where
>> eth0 is internal net
>> CONFIG proxy.config.http.server_port INT 3129
>> CONFIG proxy.config.http.server_port_attr STRING>
> 
> Ah, ok, so it might be something with the transparent code. Hopefully 
> Alan (amc) is reading this, and can answer :).
> 
> Any other problems with v2.1.5 so far? We're working towards stability 
> in both code and APIs, v2.1.6 should be the last version where we break 
> any APIs, and v2.1.7 will solely focus on code stability I think (in 
> prep for a v3.0.0 release).
> 
> Cheers,
> 
> -- Leif