Neatly Bypassing Content Security Policy

Re:Neatly Bypassing Content Security Policy by dvirsky on Thursday July 12, 2018 @05:15AM (#17513150)

Oh, not CSP as in concurrency. Makes more sense now.

[ Parent | on HN ]

Re:Neatly Bypassing Content Security Policy by stephengillie on Thursday July 12, 2018 @08:55AM (#17513909)

If your Cloud Service Provider doesn't support Communicating Sequential Processes, would their Customer Service Personnel handle a Constraint Satisfaction Problem?

[ Parent | on HN ]

Re:Neatly Bypassing Content Security Policy by sullyj3 on Thursday July 12, 2018 @05:37AM (#17513222)

I assumed Constraint Satisfaction Problem

[ Parent | on HN ]

Re:Neatly Bypassing Content Security Policy by xenonite on Thursday July 12, 2018 @06:11AM (#17513311)

I had the same thought. It would be good to adjust the headline accordingly.

[ Parent | on HN ]

Re:Neatly Bypassing Content Security Policy by dboreham on Thursday July 12, 2018 @07:48AM (#17513635)

I came to read about how Node.js uses a single thread to bypass CSP...

[ Parent | on HN ]

Re:Neatly Bypassing Content Security Policy by djtriptych on Thursday July 12, 2018 @05:28AM (#17513192)

* Stands in this line

[ Parent | on HN ]