Re: [squid-users] Reverse proxy timeout

Thanks Amos, that did the magic!!

On Fri, Jan 31, 2014 at 6:15 AM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 31/01/2014 12:29 p.m., Boaz Citrin wrote:
>> Hello,
>>
>> I request a page directly from my server and all works fine.
>> Same request through Squid as a reverse proxy I get a timeout.
>> Squid version is 2.7.STABLE8 running on Windows 7 64-bit.
>>
>> The request is pretty standard:
>>
>>> GET /_fti/local/viz_data_hub/_design/lucene/search?q=%28directory:%22/directory/id/urn:uuid:63e5cd29-a2c0-43b9-a8fe-df4e85579c9b%22%29&skip=0&limit=50&include_docs=true HTTP/1.1
>>> User-Agent: curl/7.26.0
>>> Host: localhost:5984
>>> Accept: */*
>>
>>
>> My server, when requested directly, returns the following headers:
>>
>> < HTTP/1.1 200 OK
>> < Vary: Accept, Accept-Encoding, User-Agent
>> < Transfer-Encoding: chunked
>> < Server: Jetty(8.1.14.v20131031), CouchDB/1.2.1 (Erlang OTP/R14B04)
>> < ETag: d2efc8de394f
>> < Date: Thu, 30 Jan 2014 22:59:28 GMT
>> < Content-Type: text/plain;charset=UTF-8
>> < Cache-Control: must-revalidate
>
> HTTP/1.1 chunked encoding is not fully supported by Squid older than
> version 3.1. Squid-2.7 should be sending a HTTP/1.0 request to the
> server and HTTP/1.1 says servers MUST NOT send chunked encoding back to
> any 1.0 client.
>
>
>>
>> This is the relevant part from Squid config, all the rest is the default:
>>
>> http_port 5986 accel defaultsite=couchdb
>> cache_peer localhost parent 5984 0 no-query originserver name=couchdb_server
>
> You could try adding the "http11" option to the cache_peer line and
> seeing if your Squid can handle the server responses better. If that
> does not work you will need to fix the server itself not to send the
> chunked encoding to HTTP/1.0 clients.
>
> Amos
Received on Fri Jan 31 2014 - 11:50:37 MST