[Webkit-unassigned] [Bug 98838] New: XHR CORS on 302 Redirect doesn't set Origin in request

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 9 18:00:01 PDT 2012


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

           Summary: XHR CORS on 302 Redirect doesn't set Origin in request
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Major
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: terinjokes at gmail.com


Chrome Version       : 24.0.1284.2 dev
Safari Version       : 6.0.1 (8536.26.14)
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
 Firefox 15.x: OK
         IE 8: OK

What steps will reproduce the problem?
0. Be on one domain (host: http://example.test)
1. Initiate a XHR CORS request to a resource. (host: http://test1.example.org)
2. The resource issues a 302 redirect to another resource on another domain (host: http://test2.example.org)

What is the expected result?
The second request (to test2.example.org) would have set the Origin to "example.test" in the request

What happens instead?
During the second request the Origin is set to "null"

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list