Re: [squid-users] NONE/501 in an https:// POST request

On 12/01/11 23:37, Ralf Hildebrandt wrote:
> From my log:
>
> 1294680915.190 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294681815.209 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294682115.216 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294682715.230 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294683315.245 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294683615.251 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294684815.280 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
> 1294685115.286 0 10.43.120.109 NONE/501 4145 POST https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL - HIER_NONE/- text/html
>
> The User is getting this page:
>
> *** SNIP ***
> Der folgende Fehler wurde beim Versuch die URL
> https://enis.eurotransplant.nl/donor-webservice/dpa?WDSL zu holen
> festgestellt:
>
> Anfragemethode und Protokoll nicht unterstützt
>
> Squid unterstützt nicht alle Anfragemethoden für alle Protokolle. Sie
> können zum Beispiel keine POST Anfrage über das Gopher Protokoll senden.
> *** SNIP ***
>
> which is "ERR_UNSUP_REQ" in German!
>
> Squid does not support all request methods for all access protocols.
> For example, you can not POST a Gopher request.
>
> What I don't understand:
>
> 1) It's https:// -- why am I seeing the URL? Usually I'm just seeing
> CONNECT and a target IP with HTTPS!

* Possibly they were using some non-SSL capable tool or web app.
* Maybe you have a mystery child proxy using ssl-bump feature.

Either way it should work if you have SSL support built into this Squid.
But won't if not.

>
> 2) Why EXACTLY is it failing? I'd like to debug this further :)
>

Possibly some bad mix of chunked encoding. But, I'm thinking the SSL
support is missing. CONNECT does not actually involve SSL, just pumping
bytes across a TCP tunnel link.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.10
   Beta testers wanted for 3.2.0.4