Skip to content
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

Server-side HTTP caching improvements [SPR-11792] #16413

Closed
spring-issuemaster opened this issue May 15, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@spring-issuemaster
Copy link
Collaborator

commented May 15, 2014

Brian Clozel opened SPR-11792 and commented

This is an umbrella issue for several improvements on HTTP caching strategies.

Those improvements include:

  • Refactor WebContentGenerator to decouple HTTP Headers from each other and enable flexible use of last-modified, must-revalidate, Cache-Control: public/private, no-transform
  • Decoupling HTTP caching features from WebContentGenerator and explore alternative solutions
  • Provide controller method-level alternative to WebContentInterceptor
  • Enable gzip compression in DispatcherServlet

References: Mark Nottingham's cache docs and RFC2616


Sub-tasks:

  • #7466 HTTP caching should be decoupled from WebContentGenerator
  • #11500 Add support for no-transform cache control header
  • #11789 Add support for public/private Cache-Control HTTP header
  • #13194 Provide controller method level alternative to WebContentInterceptor
  • #14177 Use same pragma settings in WebContentGenerator as in AbstractView
  • #15097 Allow must-revalidate to be suppressed in ResourceHttpRequestHandler
  • #15948 ServletWebRequest can't validate Etag and Last-Modified together.
  • #16336 gzip compression in DispatcherServlet

Issue Links:

  • #17799 WebContentGenerator not backwards compatible
  • #17843 Reset Pragma header in WebContentGenerator when caching resources
  • #18625 Reset Expires header in WebContentGenerator when caching resources
  • #17844 Document changes about HTTP cache header defaults in migration docs
  • #10491 HTTP cache and conditional requests support in RestTemplate
  • #16988 ResourceHttpRequestHandler serves all files with must-revalidate cache header, should not do that when using a content versioning strategy

6 votes, 16 watchers

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 7, 2014

Oliver Drotbohm commented

FYI, there has been an updated RFC for HTTP caching which we might wanna/need to consider.

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 11, 2014

Brian Clozel commented

Thanks Oliver Drotbohm!
I've seen this as well. It looks like it's mainly clarifications, but we should consider this and either:

  • make additional adjustments if needed
  • postpone this to 4.2 as part of a broader feature update for HTTP (+ HTTP/2?)
@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Mar 23, 2015

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented May 20, 2015

Juergen Hoeller commented

Resolving this umbrella issue for the purposes of 4.2 RC1. #10491 now remains as a separate but related improvement.

@spring-issuemaster spring-issuemaster added this to the 4.2 RC1 milestone Jan 11, 2019

This was referenced Jan 11, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.