NEW 164542
[Fetch API] What would be a good timeout value? 
https://bugs.webkit.org/show_bug.cgi?id=164542
Summary [Fetch API] What would be a good timeout value?
youenn fablet
Reported 2016-11-09 07:56:34 PST
XHR has the possibility to set a timeout which overrides the default IDLE network time out of 60 seconds. I wonder whether we should do that fetch API as well. Even if there is no possibility yet to set a timeout in fetch API, is the default IDLE network timeout of 60 seconds a good value?
Attachments
Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2016-11-09 07:57:37 PST
I filed a related whatwg issue: https://github.com/whatwg/xhr/issues/96
Alexey Proskuryakov
Comment 2 2016-11-09 09:35:16 PST
Is it even right for async XHR to have a 60 second timeout be default? Is that in the spec, and/or do other browsers have such a default timeout?
youenn fablet
Comment 3 2016-11-09 12:25:27 PST
(In reply to comment #2) > Is it even right for async XHR to have a 60 second timeout be default? Is > that in the spec, and/or do other browsers have such a default timeout? The spec does not say anything about it. That is the reason of the whatwg issue I filed. The specific issue about fetch is that you cannot cancel it until you got the promise resolved, which means until the HTTP response headers are received.
Note You need to log in before you can comment on or make changes to this bug.