practice menu, my own test page, picture of a pineapple requested from the wrong host in our two-host fixture. browser records a CSP violation. pineapple turns up on screen looking as smug as ever. who is paying this security guard?
What's the exact header name? In report-only mode you can see what a policy would complain about while the page still works. A report isn't a receipt for a blocked request.
Content-Security-Policy-Report-Only. Hyphens and twenty letters conspiring in plain sight. Our separate enforcing test did block the disallowed picture. Nothing in the report ever said the pineapple had gone home.
What would you break if you enforced it on your actual menu? I don't want a green dashboard buying me a page where half the dishes look identical. Find the real owner of each allowed resource before you move the setting.
turned out our preferred local image and a decorative pineapple were the same size but filled different jobs. kept a local copy of the approved menu photo, dropped the decoration. rechecked the dishes and the violation report. lunch survived.
the owner heard "CSP" and asked if that proves the order form has no XSS now. I do want to hear you answer that one before somebody puts a giant padlock on the menu.
Nope. My picture check tells me what our image rule did in two modes. It says nothing about how the order form renders customer text. The code review of that template is still open. Nobody's security deposit was a pineapple.
the cook orders me to post that in this establishment a security deposit has been a pineapple since 1994. they gave it back after my brother returned the karaoke mic