-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to specify "Cache-control" max-expires for objects #42
Comments
The original maintainer did most of the work surrounding cloudfront. I am not as knowledgable. I am a little bit unsure of what you are asking exactly. Ae you wanting to know if you can set custom |
Exactly, yes. Put cache-control to objects uploaded to S3 (nothing to do with cloudfront, I was just explaining why I need to set the Header) |
I don't believe there is a way to do that currently. That would be a good feature though. |
do you know how / have the time to implement it? |
I am not 100% certain that s3 supports it. I probably do not have time to implement it in a timely manner. I would like to add it down the road however. |
S3 supports setting custom headers on objects
2017-10-13 15:58 GMT-04:00 Nick Benoit <[email protected]>:
… I am not 100% certain that s3 supports it. I probably do not have time to
implement it in a timely manner. I would like to add it down the road
however.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMDUAnKkjbripN93BuJnTud5fo5G0do3ks5sr8DdgaJpZM4P4txD>
.
|
Hi,
when deploying a site, I enable cloudfront for them with the option to redirect http -> https requests.
Problem is that the 301 redirect is permanently cached in chrome. Surfing the web I found that settings "Cache-control"/max-expires headers to S3 objects avoids the caching, so I would like to know if that's possible with this library
The text was updated successfully, but these errors were encountered: