[
https://issues.apache.org/jira/browse/TS-4700?focusedWorklogId=26952&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26952
]
ASF GitHub Bot logged work on TS-4700:
--------------------------------------
Author: ASF GitHub Bot
Created on: 23/Aug/16 18:49
Start Date: 23/Aug/16 18:49
Worklog Time Spent: 10m
Work Description: Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/895
I'm ok with this, but it's slightly misleading that we are changing both
the HTTP/1 and the H2 timeouts. Perhaps considering mentioning this in the
commit message body, or the Summary? It'll help writing the release notes for
7.0.0 I think.
But, :+1:
Issue Time Tracking
-------------------
Worklog Id: (was: 26952)
Time Spent: 40m (was: 0.5h)
> Change the default timeout for HTTP/2
> --------------------------------------
>
> Key: TS-4700
> URL: https://issues.apache.org/jira/browse/TS-4700
> Project: Traffic Server
> Issue Type: Improvement
> Components: Configuration, HTTP/2
> Reporter: Bryan Call
> Assignee: Bryan Call
> Fix For: 7.0.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> At the HTTP Workshop Patrick McManus stated that Firefox using a timeout of
> 115 seconds for HTTP/2 and likes to close the connection before they normally
> see a 120 second timeout on server. They don't want to have a race condition
> with the server.
> It would be better that was set the default timeout to 120, so we don't have
> issues with race connections and Firefox.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
