Score:0

Security Headers X-XSS-Protection issue

us flag

Is there any issues coming from adding 'Strict-Transport-Security' and 'X-XSS-Protection' headers ?

Header set Strict-Transport-Security "max-age=10886400;
Header set X-XSS-Protection "1; mode=block"

I didn't put 'include Subdomains' for the HSTS header because I wasn't sure if we always want those over HTTPS. Specifically I could see this causing issues with HubSpot and/or CDN pages (slowing down the CDN delivery, not resolution issues).

modern browsers may not even implement XSS filtering right ?

if I'm not wrong Modern browsers prefer this right ? https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy

Our WAF will block XSS injections as well so the header wouldn't actually come into effect.

Is CSP policy implementation will help ? what is the best advise here ?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.