Re: [squid-users] upgrading Squid 2.5S3 to 2.5S7 broke RealVideo

On Tue, 1 Feb 2005 23:20:34 +0100 (CET), Hendrik wrote:
>>On Mon, 31 Jan 2005 adam-s@pacbell.net wrote:
>> We recently upgraded our Squid server from a Sun Ultra60 running
>> Solaris 2.8 to a Sun V240 running Solaris 2.9. I also took the
>> opportunity to upgrade Squid from 2.5STABLE3 to 2.5STABLE7. Now our
>> streaming video (Real Media) no longer works (it hangs).
>
>Please verify that it really is the Squid upgrade and not the OS upgrade
>causing your problems. You can easily do this by either run the new
>Squid version on your old server or the old Squid version on your new
>server..

Thanks for the great idea Hendrik. I installed each version that
wasn't already tehre on the other server on a different port so I have
both versions running on each server. What we found was that either
*all* versions work for a user or they all *don't* work. So I've
misidentified the problem and apologize for that.

However we've narrowed the problem down to a particular site's Real
Media archives: http://www2.courtinfo.ca.gov/cjer/aoctv/archives.htm.
The older files (e.g. April 13, May 11th, etc.) are RealMedia and fail
to load for a user. Users for whom these files fail can view other
RealVideo files like from ABC.com, Real.com themselves etc. hence we
think it is this sites use or configuration of RealMedia.

For users who can't view the files there is a crazy work-around: if we
allow that user to unproxy themselves and then grab even the beginning
of a RealMedia TV program, then it works. And then, here is the
kicker, the user can go back to using the proxy and ALL the other
files load/view fine for that user after that (i.e. even one's he/she
has never viewed). So I suspect there is some kind of initial
handshake problem. Our webmaster is in contact with the site owners
(and their 3rd party content provider) to see if maybe they are doing
some side-band stuff. Our contact said that they use port 80 to
serve the content but may use port 1964 to setup communication so I
put that in the list of http ports squid accepts, restarted squid and
still it fails for users who have never unproxied as a work-around.
Again, once they unproxy for even just the start of one RealMedia TV
program, then they can go back to being proxied. The WindowsMedia
files (the newer dates at the above site) all play fine.

So I suspect it is a port problem but don't know how to fix it. We've
eliminated the firewall as the culprit because the (internal access
only) DEV squid proxy now has wide open access (any/any) for
connecting to the outside and it still fails there, even with port
1964 added to the accepted http ports.

So I apologize for misidentifying the problem. We are working with
the site but they don't have much info/help so I was hoping someone
here might have encountered something similar - info or a pointer to a
previous thread where this is discussed/fixed would be much
appreciated.

thanks all,

Adam
Received on Wed Feb 02 2005 - 20:29:10 MST