reschke commented on PR #499: URL: https://github.com/apache/httpcomponents-core/pull/499#issuecomment-2899223046
> The fact that QUERY is technically a different method doesn't eliminate the inconsistencies; it just shifts them. Introducing QUERY as a workaround for the issues with GET bodies assumes the entire HTTP ecosystem will uniformly recognize and support it. In reality, infrastructure like proxies, caching layers, and older servers are unlikely to know what to do with QUERY requests. This could lead to dropped requests, unexpected stripping of bodies, or flat-out rejections, similar to the problems you're trying to avoid with GET and a body. Simply put, anything that doesn’t explicitly recognize QUERY may mishandle it. That is not true. Since WebDAV, the ecosystem has learned that OPTIONS, HEAD, and GET are special (and so say the specs). All other methods have the same characteristics with respect to how request bodies are handled. And that's good, otherwise it would be impossible to introduce new methods. QUERY has the same characteristics as any other non-special method, be it PUT, PATCH, POST or PROPFIND, PROPPATCH, SEARCH, REPORT, etc. The only new thing here is that it's a safe request method with request body; it's the same as PROPFIND, SEARCH, or REPORT (fwiw, these should be marked as safe and idempotent here, should I open an issue and attach a PR?) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org For additional commands, e-mail: dev-h...@hc.apache.org
