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

Improve HTTP support and update with new HTTP RFCs [SPR-11886] #16505

Closed
spring-issuemaster opened this issue Jun 19, 2014 · 1 comment

Comments

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

commented Jun 19, 2014

Brian Clozel opened SPR-11886 and commented

This is an umbrella issue.
Sub-issues will be created as we find discrepancies in the current implementation vs. new RFCs.


Reference URL: https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead

Issue Links:

  • #16683 Update references to RFC 2616
@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

commented Sep 17, 2014

Sébastien Deleuze commented

#16683 has already been completed as part of our 4.1.RELEASE, its scope was documentation update and deprecation of:

  • HttpStatus.USE_PROXY
  • HttpStatus.REQUEST_ENTITY_TOO_LARGE in favor of HttpStatus.PAYLOAD_TOO_LARGE
  • HttpStatus.REQUEST_URI_TOO_LONG in favor of HttpStatus.URI_TOO_LONG

The remaining work to be completed in this issue is about analyzing these new RFC and Spring code base in order to identify if there are some new or updated behavior to implement.

Please notice that there is at least one remaining reference to RFC 2616 in the [MimeType](https://github.com/spring-projects/spring-framework/blob/master/spring-core/src/main/java/org/springframework/util/MimeType.java#L65) class. I did not change it as part of #16683 since it may change our implementation (not sure, to be verified).

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.