--maxage option not working?
See original GitHub issueI have the following in package.json
:
"start:dev": "sirv public --single --dev --host 0 --port 8080 -m 0"
However, the response headers lack cache-control
. Is this a bug or did I misunderstand the usage of -m/--maxage
?
On a related note, wouldn’t it make sense to always pass a no cache header in dev mode?
Issue Analytics
- State:
- Created 4 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Access-Control-Max-Age not working with Authorization header
If Authorization is incompatible with Access-Control-Max-Age is it such a bad idea to include the auth token in the body rather than as...
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 >maxAge doesn't work as expected · Issue #609 - GitHub
This token when signed has an iat of 1, exp of 36000. Validation clockTimestamp is set to 1 so as it's validating it...
Read more >maxage option in logrotate not working as expected
So I tried maxage option in logrotate but it is not working as expected. Let say I have 6 logs which is created...
Read more >Express session middleware
Note If both expires and maxAge are set in the options, then the last one defined in the object is what is used....
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 FreeTop 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
Top GitHub Comments
🎉
Available on the new
next
version for both packages:sirv-cli@1.0.0-next.1
sirv@1.0.0-next.1
Thanks!