|
Home > Archive > Squid > April 2004 > [squid-users] RTSP DESCRIBE METHOD ByPassing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[squid-users] RTSP DESCRIBE METHOD ByPassing
|
|
| James MacLean 2004-04-29, 6:55 pm |
| Hi Folks,
Any way to have squid-2.5.STABLE5 _not_ error out when an RTSP DESCRIBE
method is generated. We see Darwin/Apple servers out there setup for rtsp
over port 80. Squid replies with a 400 Bad Request and cache.log has:
clientReadRequest: FD 10 Invalid Request
This was after I added the extension_methods DESCRIBE line.
I expect this has been explained before as it must be quite common but I
could not find it in the archives  .
I've tried no_cache, and allow_direct.
JES
--
James B. MacLean macleajb@ednet.ns.ca
Department of Education
Nova Scotia, Canada
| |
| Henrik Nordstrom 2004-04-29, 6:55 pm |
| On Tue, 27 Apr 2004, James MacLean wrote:
> Any way to have squid-2.5.STABLE5 _not_ error out when an RTSP DESCRIBE
> method is generated. We see Darwin/Apple servers out there setup for rtsp
> over port 80. Squid replies with a 400 Bad Request and cache.log has:
You are running interception proxying right? If so then you need to add
rules bypassing the interception for each server abusing port 80 for
non-HTTP traffic.
Regards
Henrik
|
|
|
|
|