Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Best practice regarding Security-Relevant HTTP Headers
#2
Hi Magnus. I have suggestions to you add in your headers:
Code:
Referrer-Policy  ->  same-origin
Strict-Transport-Security  ->  max-age=15768000; includeSubDomains; preload
X-Content-Type-Options  ->  nosniff
X-Permitted-Cross-Domain-Policies  ->  master-only
X-XSS-Protection  ->  1; mode=block
Now, i suggest you be careful and test all your application running all forms with console opened.
Code:
Content-Security-Policy  ->  default-src 'self' https: 'unsafe-inline' 'unsafe-eval'; img-src 'self' https: data:; object-src https 'self'; media-src 'self' https:; style-src 'self' https: 'unsafe-inline'; script-src 'self' https: 'unsafe-inline' 'unsafe-eval'; frame-ancestors https: 'self' *.facebook.com; base-uri 'self' https:
This is working FOR ME, make all your adjustment for your needs.
Reply


Messages In This Thread
RE: Best practice regarding Security-Relevant HTTP Headers - by Jose Nilton Pace - 10-09-2019, 11:55 AM

Forum Jump:


Users browsing this thread: 1 Guest(s)