- From: Traxx <notifications@github.com>
- Date: Tue, 19 Nov 2024 05:35:27 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 November 2024 13:35:31 UTC
Another point that shows how absurd this is: I'm making a GUI rest client as a convenient testing tool embedded in an IDE. So I'm not even the one deciding on the request or its semantics, I'm just providing a tool for others to use. And now, because of this, I basically have to hand this hostage situation to everyone using my plugin and suddenly I - who is in no position to interfere with what my users wanna do with the client - have to enforce non-standard behavior when such a plugin should be as flexible as it can be. Not allowing GET bodies is not rooted in caution. It's certainly not rooted in standard compliance. By now, I'm pretty confident it's rooted in stubbornness and pride. If it breaks legacy code - don't use GET bodies when interacting with those systems. It's that easy. -- Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/551#issuecomment-2485734217 You are receiving this because you are subscribed to this thread. Message ID: <whatwg/fetch/issues/551/2485734217@github.com>
Received on Tuesday, 19 November 2024 13:35:31 UTC