Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expect-CT: put max-age first
See original GitHub issueIt’s a little weird that max-age comes second after enforce:
We should reorder these lines and update the tests.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
A new security header: Expect-CT - Scott Helme
If with the 30-second max-age, it was confirmed that the SCT is valid, the user should be fine to then set that max-age...
Read more >Access-Control-Max-Age - HTTP - MDN Web Docs
The Access-Control-Max-Age response header indicates how long the results of a preflight request (that is the information contained in the ...
Read more >Adding Expect-CT header to HTTP response
In the security test report, I have a recommendation to add Expect-CT header to the HTTP response from web ...
Read more >Expect-CT Extension for HTTP RFC 9163 - IETF Datatracker
The first time a UA connects to a host, it lacks the information ... (A max-age directive need not appear in every Expect-CT...
Read more >Caching Header Best Practices - Simon Hearne
Always set the Cache-Control header, preferably with the value max-age=31536000,immutable alongside unique asset filenames (or no-cache for non- ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Helmet 4 (and
expect-ct@1.0.0) was just released, so feel free to go ahead with your change. No rush, though!Closed by #264.