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

+1 enable GET bodies please.  Even if it's not strictly spec'd, it's as good as an undocumented industry standard in 2024.  You can add Akamai, Palo Alto, and ServiceNOW to the list of platforms that support HTTP GET body parameters in their APIs.  There are other large players doing the same.  The mislabeling of such practice as 'abuse' is wishful thinking, IMO.

I stumbled across this debacle when trying to migrate from jQuery's $.ajax() into a vanilla-JS solution, considering it's 2024 and jQ has been all-but-replaced by modern JS: see youmightnotneedjquery[.]com.  

Instead of 'muddying' my JS GET requests with mile-long parameters visible in the URL, I much prefer the encapsulation of parameters in the request body similar to a POST request.  That said, I do NOT support the concept of security through obscurity.  Instead, this approach makes the UX cleaner without mandating server rewrite rules or other 'after the fact' changes.

All available web server offerings + PHP's native interpreter already successfully handle this data today, regardless if URL-encoded or request body encapsulated.  

You've created a roadblock where one doesn't need to exist in order to argue standards semantics.  Can you imagine the backlash in the prime of jQuery if the devs had said, "No, I want you to do it this way"?

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

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