Far future expiration date [closed] Far future expiration date [closed] nginx nginx

Far future expiration date [closed]


Assuming you are talking about the Cache expiration date, the answer as Alexey Ten is "you can't".

Those resources are not controlled by you, nor on your servers. They are loaded by the browsers from external servers, therefore you have no control over them. The expiration header is set by the server that serves the asset.

In some cases you can proxy the resource (aka put a custom layer between the resource and the client), so that you can configure the cache via the proxy. But I'm not sure in this case it's a recommendable option.