Re: [whatwg/fetch] Request with GET/HEAD method cannot have body. (#551)

> this has not been fixed ... I cant send body using get method using fetch ... thank you so much for the lessons on fake security ... now please enable sending body through get request.

Seriously!!!! I honestly can't believe I read all this, to conclude that `HttpGet` is completely useless over BS semantic reasons. I found this thread simple because I wanted to be more semantically aligned for my RestAPI while dynamically coding security across the HTTP requests.

Just to annoy such a dumb ass decision, I am going to make everything `POST` from now on but I will reroute everything on the intended semantics: HttpPost("Get"), HttpPost("Put"), HttpPost("Post"), and HttpPost("Delete"). 🤣 🤣 🤣 🤣 Might even modify the HttpClient so it only does Post with the reroutes in mind.

This idea seems like a NuGet package just waiting to be made. Maybe change the naming convention from "Http" to "Rest": RestClient, RestGet, RestPut, RestPost, RestDelete... that way we can always send a body while still fulfilling our desires as developers —after all, we break semantics all the time anyway because of dumb stuff like this and make our own. With some time get Swagger updated with this concept in mind.

In the end, we will get what we want.

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

Message ID: <whatwg/fetch/issues/551/2324975958@github.com>