[Webkit-unassigned] [Bug 149704] New: Default network timeout may kick in before XHR timeout

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=149704

            Bug ID: 149704
           Summary: Default network timeout may kick in before XHR timeout
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebCore Misc.
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: youennf at gmail.com

As pointed out by ap in bug 98156, http://trac.webkit.org/changeset/189445 introduces the fact that default networking timeout becomes a max timeout for all XHR requests.

If a web app sets a XHR timeout above the default network timeout, the default network timeout will kick in.

Setting networking timeout to infinite (or a sufficiently large value) for all XHR requests may work.

Setting networking timeout to infinite for all XHR requests that have their own timeout may work.
In that case, one may want to add special handling for the case of a web app that sets back the timeout to zero.
Ideally, the XHR timer should then be set to the default networking timeout value.
Infinite may be good enough, although not entirely satisfying.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20151001/fe2bd16f/attachment.html>