HTTP Security Headers – A Complete Guide

Re:HTTP Security Headers – A Complete Guide by BCharlie on Thursday July 18, 2019 @11:11AM (#20470632)

You are right on this - I thought you could set multiple sites by setting multiple headers, but it doesn't work that way, which I should have known because headers don't work that way in general...

The recommended way to do multiple sites seems to be to have the server read the request header, check it against a whitelist, then dynamically respond with it, which seems terrible.

Thanks for catching this - I updated the post to reflect this and make it more clear.

[ Parent | on HN ]

Re:HTTP Security Headers – A Complete Guide by unilynx on Thursday July 18, 2019 @01:43PM (#20472196)

Actually, headers _do_ often work that way. HTTP says:

Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list

Which applies to HTTP headers such as Cache-Control:, and probably goes back to the email RFCs allowing multiple To: headers.

It's just that Access-Control-Allow-Origin isn't defined to accept a comma list, just like Content-Security-Policy doesn't (which is another header breaking things if it appears more than once)

[ Parent | on HN ]

Re:HTTP Security Headers – A Complete Guide by paulddraper on Friday July 19, 2019 @11:50PM (#20484097)

Headers usually work exactly that way. Cookies and cors are oddball exceptions

[ Parent | on HN ]