On Mar 15, 2014, at 11:48 PM, Marcelo Gotesdiner <[email protected]>
wrote:
> Hi,
>
> I’m having problems to configure ATS to work with persistent connections.
> According to the documentation, with HTTP 1.1, it should be the default
> behavior.
> I also checked in records.config :
> CONFIG proxy.config.http.keep_alive_enabled_in INT 1
> CONFIG proxy.config.http.keep_alive_enabled_out INT 1
> CONFIG proxy.config.http.chunking_enabled INT 1
> CONFIG proxy.config.http.keep_alive_no_activity_timeout_in INT 115
> CONFIG proxy.config.http.keep_alive_no_activity_timeout_out INT 120
> CONFIG proxy.config.http.origin_min_keep_alive_connections INT 200
>
> And everything looks fine.
>
> But, for some reason, when an error response is sent, the connection is
> closed.
> I captured several tries with tcpdump (below the wireshark picture) and I can
> see the FIN immediately after the client ACK …
I believe some errors are considered “unrecoverable”, and as a defensive
mechanics, causes forceful shutdowns, e.g.
HTTP/1.1 404 Not Found on Accelerator
Date: Sun, 16 Mar 2014 20:55:19 GMT
Connection: close
Check your responses, and see if it’s not doing a Connection: close on you?
Cheers,
— leif
