A bug by StoreID when using cache_peer?

OK I have been playing around while debugging some strange uncaching of
objects and I have found out that I get on a parent proxy a request like
this:
----------
2014/04/25 02:17:00.074 kid1| client_side.cc(2407) parseHttpRequest:
HTTP Client local=192.168.10.134:3128 remote=192.168.10.103:46511 FD 14
flags=1
2014/04/25 02:17:00.074 kid1| client_side.cc(2408) parseHttpRequest:
HTTP Client REQUEST:
---------
GET
http://yt.video.squid.internal/id=o-ALDnT-e6tRpOr110wVK7tbUzpi-hCxi7_kImNWccRy4j&itag=134&range=0-1144831
HTTP/1.1
Host: r8---sn-nhpax-ua8l.googlevideo.com
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:28.0) Gecko/20100101
Firefox/28.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://s.ytimg.com/yts/swfbin/player-vfle1V0w6/watch_as3.swf
X-Forwarded-For: 192.168.10.99
Cache-Control: max-age=1728000
Connection: keep-alive

how on earth??
Downstream proxy with StoreID enabled and converting addresses of youtube.
Allowing YT videos traffic only throw the upstream proxy which on his
time does also StoreID.

Now after writing I see that it was fixed already in rev 13107.

OK so this is a description of the issue ^^ with some example for the
hall of fame of StoreID bugs.

Eliezer
Received on Thu Apr 24 2014 - 23:28:43 MDT