"Expires:" Header should be set to the request date #71
Milestone
Comments
rhuss
added a commit
that referenced
this issue
Mar 17, 2013
According to RFC-2616 this is the recommended way for signaling that the content should not be cached. This works for the Servlet and JVM Agent. Also added a corresponding integration test to Jmx4Perl. Fixes #71.
Fixed now, setting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we set the expires header to '-1' which, according to RFC 2616 is a possible way to mark content as stale;
This works for most clients, however Spring Rest Support seems to have a problem with this. So we should probably switch to the recommendation to set the Expire-Header to the Date of the request (or, if this value is not easily available at the place where the response is generated, at least to "0").
The text was updated successfully, but these errors were encountered: