RE: [squid-users] Please help debugging proxy problem with GET /

From: ζΕΔΟΤΟΧ α.α. <fedotov-aa_at_fsk-ees.ru>
Date: Mon, 12 Mar 2012 15:55:45 +0400

Thanks, Amos!

-----Original Message-----
From: Amos Jeffries [mailto:squid3_at_treenet.co.nz]
Sent: Monday, March 12, 2012 3:29 PM
To: squid-users_at_squid-cache.org
Subject: Re: [squid-users] Please help debugging proxy problem with GET /

On 12/03/2012 7:32 p.m., ζΕΔΟΤΟΧ α.α. wrote:
> Hi folks,
> We get the following problem with Squid configuration. Short GET or
> POST requests do not pass proxy, the proxy returns customized
> "invalid request" error message
>
> GET / HTTP/1.0\r\n
> Host: yandex.ru\r\n
> Proxy-Authorization: Basic ***\r\n
> \r\n
>
> The following works:
>
>
> GET http://yandex.ru/ HTTP/1.0\r\n
> Host: yandex.ru\r\n
> Proxy-Authorization: Basic ***\r\n
> \r\n
>
> Where to start digging? Thank you in advance!

With the difference between client->proxy and client->server HTTP formats...

"http://yandex.ru/" is an absolute-URL. For requests handled by HTTP proxies.

  "/" is a URL-path. For requests handled by origin servers and their surrogates (reverse-proxy). For example, is that a part of an http://, https://, ftp://, gopher://, or some other URI format? only the origin server or its dedicated surrogate (reverse-proxy) can know that.

Amos
Received on Mon Mar 12 2012 - 11:56:41 MDT

This archive was generated by hypermail 2.2.0 : Mon Mar 12 2012 - 12:00:04 MDT