Bug 155633
| Summary: | PotentiallyCrossOriginEnabled option should trigger setting related headers directly by the loadercode | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | youenn fablet <youennf> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | ap, bfulgham, dbates, joepeck |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
youenn fablet
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Joseph Pecoraro
I'm going to remove this comment, Youenn agrees it is outdated.