You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 10, 2024. It is now read-only.
According to RFC 7234 we should assume that this page will be cached since no Cache-Control headers are set:
Although caching is an entirely OPTIONAL feature of HTTP, it can be assumed that reusing a cached response is desirable and that such reuse is the default behavior when no requirement or local configuration prevents it.
It is not desirable that any page coming from elmrsample be cached since it is wrapped with Shibboleth, and the content itself is not designed to be cacheable. Please ensure that all pages set the following Cache-Control headers per Amazon's recommendations:
Cache-Control: no-cache, no-store
FYI This stack overflow thread gives a bunch of code examples in various languages including Java and Python. In addition, for backwards compatibility with all browers since the 90's it recommends the following settings:
For modern browsers and caches the settings recommended by Amazon are sufficient. You can find more information about these directives from the RFC here. I will leave it to you to decide which recommendation to follow. I will test for no-cache, no-store.
The text was updated successfully, but these errors were encountered:
When I performed a curl against
auth/elmr/session
, I received the following headers:According to RFC 7234 we should assume that this page will be cached since no
Cache-Control
headers are set:It is not desirable that any page coming from
elmrsample
be cached since it is wrapped with Shibboleth, and the content itself is not designed to be cacheable. Please ensure that all pages set the followingCache-Control
headers per Amazon's recommendations:FYI This stack overflow thread gives a bunch of code examples in various languages including Java and Python. In addition, for backwards compatibility with all browers since the 90's it recommends the following settings:
For modern browsers and caches the settings recommended by Amazon are sufficient. You can find more information about these directives from the RFC here. I will leave it to you to decide which recommendation to follow. I will test for
no-cache, no-store
.The text was updated successfully, but these errors were encountered: