You would be surprised how many technologies expect GET with a body. In practical backend engineering, tools like Elasticsearch, GraphQL, complex query engines, and legacy internal APIs rely on GET with a body every day. Apparently even axios messes up on curl GET requests with a body as mentioned in the associated github issue.

Perhaps the broken thing might be how you expect existing softwares to break so that your expectation can be satisfied. You should look at GET more closely.

There is a reason curl allows to send GET requests with a body. There is a reason node allows to receive GET requests with a body.

▲

pdpi 4 hours ago | parent [-]

A request body in a GET is not standard HTTP. Refusing to handle non-standard requests might be inconvenient, but it's an eminently defensible choice.

I understand why you'd want it, and that's why RFC10008 introduces QUERY as a GET-with-body alternative.

	▲	elendilm an hour ago \| parent \| next [-]
		QUERY, added in 2026, does not resolve existing or legacy applications. Sticking to RFC is one thing. Advertising as node compatible is completely different altogether. Many people cannot see the difference. Atleast a flag would suffice as that would ensure existing infrastructure tooling doesn't break while keeping the RFC spec folks happy.
	▲	what 3 hours ago \| parent \| prev [-]
		Technically every http method can have a body? But the specification says the semantics are undefined on get and any compliant implementation is free to ignore it.