Comment by pdpi

1 day ago

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.

4 comments

pdpi

Reply
what  1 day ago

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.

  • elendilm  11 hours ago

    Or any compliant implementation is free to not ignore it like istio/envoy, infrastructure tooling, etc.

    What is the use of spec adherence if it leads to unusable/broken applications.

    • what  3 minutes ago

      What? The applications are broken, they don’t get to assign meaning to a get body and force every compliant implementation to play along.

elendilm  20 hours ago

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.