Re: [whatwg/fetch] non-null body with GET/HEAD requests (Issue #1705)

> Yes, we're well aware that some applications (e.g., Elasticsearch) do use bodies on GET. That is not interoperable on the open web; it only works in closed systems that, effectively, are not HTTP. While some might think that their deployment qualifies as such, it's rarely the case, because most people do not control every possible HTTP system and component that the messages might ever be handled by (eg load balancers, virus scanners, WAFs). Doing so also reduces the choice of tools and implementations that can be used in that deployment, reducing the value of using HTTP.

FWIW, Cloudflare supports bodied GETs throughout its stack. In Workers specifically, it was very early on that we were forced to support this due to user complaints. So my expectation is that any HTTP proxy product is wide use is probably forced to support bodied GETs and therefore such support is a de facto standard.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1705#issuecomment-1737510103
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1705/1737510103@github.com>