Avishaa Anu
Reputation: 1
Strict Transport Security Not Enforced fixed in IIS but still insecure
I configured HSTS in HttpResponseHeaders giving value as maxtime = 31536000 but still showing insecure popup in URL and using HTTP
given name="Strict-Transport-Security" value="max-age=31536000; includeSubDomains; preload" in HTTP Response Headers.
Upvotes: 0
Views: 25
Answers (0)
Related Questions
- Checkmarx: Missing HSTS Header in React Application
- Strict-Transport-Security Header only have max-age
- How strict transport security header should applied on www subdomain?
- Angular Preflight Request to Add Headers
- HSTS (HTTP Strict Transport Security) on Node-red
- How to set the strict transport security header for jetty 9.2.25
- Adding HTTP Strict Transport Security to .htaccess
- Is it fine to use duplicate response header with same value?
- Remove HTTP Strict Transport Security (HSTS) response header in spring oauth2 token API