Max-age=0 header issue

[yoginth]

Assets and caching

I was surprised to find that assets are served with a Cache-Control: max-age=0 header, which means that the browser will always revalidate them. Glitch seems to append a timestamp when copying an asset’s URL to the clipboard, shouldn’t it then be safe to give assets a long max-age like 1 year?

Still this issue is not yet fixed

[DanielX]

In this case it is your Express server setting the header. You can modify your server code to set it to whatever is appropriate for your application. If you have questions about how to do this specifically in the case of your application please “Raise your hand” and a member of our friendly and helpful community will be there to assist you!

[yoginth]

Yeah please help me how to do it!

[Gareth]

There’s some useful examples here: https://github.com/expressjs/serve-static/issues/32#issuecomment-76226945