There is a bug for these settings where the timeout was actually TTFB and not a timeout for completion of three-way handshake:
https://issues.apache.org/jira/browse/TS-242 https://github.com/apache/trafficserver/pull/4028 One reason to set POST timeouts much longer than GET timeouts is due to the asymmetric nature of home broadband connections. For example, on a site with user generated content it might take a lot longer to upload a video than to download the same video. I'm guessing the TTFB vs connect bug + slower upload speeds? David On Tue, Aug 21, 2018 at 8:18 PM, Nishant Gaurav <nishant16...@gmail.com> wrote: > Hi, > > I see that there is a large difference b/w the default value of timeout for > GET and POST (and PUT) requests (in seconds). > > CONFIG proxy.config.http.connect_attempts_timeout INT 30 > CONFIG proxy.config.http.post_connect_attempts_timeout INT 1800 > > I couldn’t think of a reason why it should be that different. We are trying > to tune some parameters, and were wondering the rationale behind these > config values. > > Regards, > Nishant >
