[squid-users] Streaming audio header info

This might sound a bit vague, as I have just picked up support for
squid.

We are currently running squid-2.5.STABLE1 on a Solaris 5.5.1, with
local password authentication. I am in the processes of replacing it
with a Solaris 9 box running squid-2.6.STABLE18, and ntlm authenticating
via samba off our DCs.

Everything seems to work fine off the new scenario, except for a couple
of users who use winamp to listen to online music etc. On the old set
up, when they listen to a site, they get the track or station info back
within winamp. Presumably some form of metadata in the header
somewhere. But on the new one, that info isn't present - all they see
is the url they are playing. Otherwise, it all works.

I can't for the life of me work out where this info is being lost. The
only difference in the log files I see is:

old working proxy:
1205225734.572 27711 <ip address> TCP_MISS/600 639404 GET
http://mp3-vr-128.smgradio.com/ <username> DIRECT/85.159.184.42 -
1205226002.900 26061 <ip address> TCP_MISS/600 582218 GET
http://mp3-vr-128.smgradio.com/ <username> DIRECT/85.159.184.42 -

new failing proxy:
1204908920.018 235 <ip address> TCP_MISS/200 7427 GET
http://mp3-vr-128.smgradio.com/ <username> DIRECT/85.159.184.42 -
1204908920.178 224 <ip address> TCP_MISS/200 8719 GET
http://mp3-vr-128.smgradio.com/ <username> DIRECT/85.159.184.42 -

Is the TCP_MISS/600 vs TCP_MISS/200 significant?

It's not really a show stopper, more of an annoyance, but I'm more
worried that the problem might manifest itself elsewhere if I have
something misconfigured.

This is not my area of expertise, and I'm a bit stumped as where to look
next......

Alan
Received on Mon Mar 17 2008 - 05:42:00 MDT