[Webkit-unassigned] [Bug 155633] New: PotentiallyCrossOriginEnabled option should trigger setting related headers directly by the loadercode

[bugzilla-daemon at webkit.org]

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

            Bug ID: 155633
           Summary: PotentiallyCrossOriginEnabled option should trigger
                    setting related headers directly by the loadercode
    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

Code that want to load resources in a cross origin manner need to set the loader option to PotentiallyCrossOriginEnabled.
It also need to set the corresponding request headers accordingly, like the origin header.
This second step would best be handled by the loaders when PotentiallyCrossOriginEnabled is set.

-- 
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/20160318/016d76b9/attachment.html>