Re: [SQU] problem in parseHttpRequest

At 14:15 22/11/00 +0100, Enrique Galdú Orduña wrote:
>It has a ^M in the URL that causes my squid to produce the
>ERR_INVALID_REQUEST error.
>The debug says:
>
>2000/11/22 13:38:13| commSetSelect: FD 13 type 1
>2000/11/22 13:38:13| parseHttpRequest: Method is 'GET'
>2000/11/22 13:38:13| parseHttpRequest: URI is
>'http://ad.es.doubleclick.net/adj/www.elpais.es/portada;abr=!ie;sz=468x6^M'
>2000/11/22 13:38:13| parseHttpRequest: Missing HTTP identifier
>2000/11/22 13:38:13| cbdataAdd: 0x88141f0
>2000/11/22 13:38:13| conn->in.offset = 0
>2000/11/22 13:38:13| commSetTimeout: FD 13 timeout 86400
>2000/11/22 13:38:13| clientReadRequest: FD 13 Invalid Request
>
>
>Is it possible to avoid this error with proper configuration of squid?

Hi

In all fairness, this is not a Squid problem. It's not Squid's fault if
A.N. Website is publishing RFC-breaking links. As far as I'm aware, Squid
only has a facility for dealing (equally RFC-breaking) white space from
URLs via the "uri_whitespace" option in squid.conf. I can't tell you off
the top of my head if ^M is included in the list.

Besides, why not just block doubleclick entirely? :)

Regards

Martin A. Brooks
----------------------------------------------
If Windows NT were an animal, it'd be a fainting goat.

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html