- From: <bugzilla@jessica.w3.org>
- Date: Sun, 01 Mar 2015 03:58:58 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28117
            Bug ID: 28117
           Summary: Clarify timeout in case Preflighted CORS requests
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XHR
          Assignee: annevk@annevk.nl
          Reporter: naren@vimeo.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
The spec needs to specify how timeout should behave when there is Preflight
OPTIONS request. It seemed logical to assume xhr.timeout = timeout (OPTIONS +
ACTUAL) request
The way browsers implement is non intuitive. Say I set timeout as 1000 (1sec).
The browser sets 1000ms timeout for OPTIONS and 1000ms timeout for ACTUAL
request. 
Clarifying that in the spec would enable browsers to implement the right way.
-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Sunday, 1 March 2015 03:59:00 UTC