X-Content-Security-Policy-Report-Only not working in Firefox 20 -


i have following content security policy defined:

x-content-security-policy-report-only: default-src 'self'; report-uri /foo 

if change x-content-security-policy, policy gets enforced , report sent. however, when set report-only, no policy warnings appear in console , no report sent.

i'm aware of bug don't support unsafe-inline , unsafe-eval, rather have use options inline-script eval-script, i'm not using either on page.

i don't know if has it, header being sent x-content-security-policy-report-only, firebug translates x-content-security-policy-report-only - changing case.

also, when supplying both x-content-security-policy , x-content-security-policy-report-only follows:

x-content-security-policy: default-src 'self'; options inline-script; report-uri /csp-report.php x-content-security-policy-report-only: default-src 'self'; report-uri /csp-report.php 

the console has warn level message:

report-only csp policy ignored because there other non-report-only csp policies applied.

so it's seeing header, , instead of processing , reporting enforcing other, it's dropping altogether?

uggh - i'd seen bug report before, didn't read , thought unsafe-inline or unsafe-eval problem. https://bugzilla.mozilla.org/show_bug.cgi?id=687086 talks inline script not firing policy because script allowed run. doing testing other things violate policy (such loading script elsewhere) report gets generated , sent.


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -