Add RFC 10008 (QUERY HTTP method) support#34993
Conversation
f640f86 to
6f9aa37
Compare
|
Will keep this one in draft until the standard is published, but I'd appreciate any review |
258303c to
e7e5a72
Compare
e7e5a72 to
95c6c7a
Compare
95c6c7a to
a723d04
Compare
7c5025d to
6c71421
Compare
|
the draft has been approved for publication, so I'm marking this PR as ready for review. |
That's a 404 now, we can use https://www.rfc-editor.org/info/rfc10008/ instead as a reference. |
|
In which spring boot version will this change be available? |
0a54a98 to
b72dd80
Compare
b72dd80 to
60c1d1b
Compare
|
We will do a thorough review of this PR and synchronize with other Spring projects. There are many aspects to consider (like the fact that |
Signed-off-by: Mario Daniel Ruiz Saavedra <desiderantes93@gmail.com>
Signed-off-by: Mario Daniel Ruiz Saavedra <desiderantes93@gmail.com>
Signed-off-by: Mario Daniel Ruiz Saavedra <desiderantes93@gmail.com>
Signed-off-by: Mario Daniel Ruiz Saavedra <desiderantes93@gmail.com>
1410d79 to
316296b
Compare
|
I understand a lot of people want this to be merged, after all, it is a very useful addition if I do say so myself. However, at this point approvals from non-committers are becoming background noise, it is hard to know if they're showing support, or if it's a form of spam. You can leave a reaction on the PR description, or track the ecosystem adoption in other projects and get involved in other areas. You can also leave a comment if you spot any issues with this implementation. Otherwise I think it'd be best to heed the comment from @bclozel and await for further updates. Thanks for your interest! |
This change introduces support for RFC 10008: The HTTP QUERY Method.
Although initially described as just a "safe GET with a body", the QUERY method unlocks the ability to send complex payloads that do not represent a mutation, and can be handled in a safe, idempotent way. Think of it as a replacement for usecases like complex query parameters in URLs, POST requests that do not mutate anything (but have to be treated as such by all other components in the network roundtrip, so no caching, etc.), and non-mutating HTML Form submission that can use an appropriate encoding for the body.
Fixes #32975