Re: [squid-users] Problem: parseHttpRequest: Requestheader contains NULL characters

On Tue, 1 Jun 2010 13:07:28 -0400, Pedro Silva <pedropes_at_gmail.com> wrote:
> Hi,
>
> In my cache.log following lines appear.
>
> 2010/06/01 12:11:10| parseHttpRequest: Requestheader contains NULL
> characters
> 2010/06/01 12:11:10| parseHttpRequest: Unsupported method ' '
> 2010/06/01 12:11:10| clientReadRequest: FD 131 (192.168.0.14:54629)
> Invalid Request
>
> These appear to see a site that does streaming. Looking for
> information should I add or modify
> the line in my squid.conf extension_methods. The problem is not
> knowing what to add parameters
> to accept streaming audio / video.
>
> Can that be a problem?. Can you help me solve this problem?

For most streaming it is not possible to solve in Squid. The problem is
non-HTTP protocol garbage being pushed into port 80.

You need to get the client agents configured to use the proxy properly or
to use their native protocol ports and not port 80.

The exception being SHOUTcast streaming which natively sends an
almost-HTTP protocol over port 80. Support has been added to Squid-3.1,
with an early experimental support also in Squid-2.7 via the
upgrade_http0.9 directive.

Amos
Received on Wed Jun 02 2010 - 00:41:59 MDT