codeinabox@programming.dev to Web Development@programming.devEnglish · 13 days agoThe HTTP QUERY Methodwww.ietf.orgexternal-linkmessage-square4fedilinkarrow-up119
arrow-up119external-linkThe HTTP QUERY Methodwww.ietf.orgcodeinabox@programming.dev to Web Development@programming.devEnglish · 13 days agomessage-square4fedilink
minus-squareNigelFrobisher@aussie.zonelinkfedilinkarrow-up3·12 days agoWhy not just allow GETs to include a body though?
minus-squareThe_Decryptor@aussie.zonelinkfedilinkEnglisharrow-up5·12 days agoBackwards compatibility, it’s never been valid to send a body with a GET, and software does enforce that (to varying levels) It’s easier to create a new verb with the wanted semantics, than to change an existing one.
minus-squareGreenKnight23@lemmy.worldlinkfedilinkarrow-up3·12 days agoyou can still send a body with a get, it’s just up to the server to accept and parse it. I suppose you could use a proxy like nginx or apache and rewrite the body to params, but that’s not really what GETs are for.
Why not just allow GETs to include a body though?
Backwards compatibility, it’s never been valid to send a body with a GET, and software does enforce that (to varying levels)
It’s easier to create a new verb with the wanted semantics, than to change an existing one.
you can still send a body with a get, it’s just up to the server to accept and parse it.
I suppose you could use a proxy like nginx or apache and rewrite the body to params, but that’s not really what GETs are for.