Talk:Security/CSP/Spec: Difference between revisions
(Comment on Trailer headers.) |
No edit summary |
||
| Line 6: | Line 6: | ||
handling a certain file type, a policy file, fall | handling a certain file type, a policy file, fall | ||
squarely in the realm of the Accept header? | squarely in the realm of the Accept header? | ||
"No inline JavaScript will execute" should probably be generalized to "No inline script will execute" as there are a number of different script-protocol handlers in different browsers, and most browsers have the ability to host script other than JavaScript. | |||
Revision as of 16:37, 24 June 2009
Allowing the X-Content-Security-Policy header "anywhere" in the response clearly isn't correct-- it must be somewhere in the response *headers*. More importantly, it might be worth explicitly specifying that the header should/must appear in the initial headers and specifically not in TRAILER headers, because otherwise the entire page must be buffered to ensure that the policy is retrieved before the user interacts with the page.
Is there an appropriate forum to discuss this? If so, please post a link. If not, is more misuse of the user-agent header the best way to go, or does handling a certain file type, a policy file, fall squarely in the realm of the Accept header?
"No inline JavaScript will execute" should probably be generalized to "No inline script will execute" as there are a number of different script-protocol handlers in different browsers, and most browsers have the ability to host script other than JavaScript.