Body handling for get and delete methods
See original GitHub issueCurrently Frisbee converts body into a query string for get
and delete
methods. That’s weird because it’s an artificial limitation and there is no way to workaround it. On the other hand it requires additional tooling to add a query string to an url.
I propose to bring get
and delete
methods in line with the rest of methods and introduce a params
option, that will stringify params and add it to url. I would be happy to send PRs!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
Is an entity body allowed for an HTTP DELETE request?
Having bodies in GET (and DELETE) is clearly mistreating HTTP and REST. There are other mechanisms for dealing with concurrency control (e.g. If-Modified-Since ......
Read more >REST - Should you use a body for your HTTP DELETE ...
According to Mozilla a DELETE request "may" have a body, compared to a PUT, which should have a body. By this it seems...
Read more >DELETE - HTTP - MDN Web Docs
The HTTP DELETE request method deletes the specified resource. Request has body, May. Successful response has body, May. Safe, No. Idempotent ...
Read more >HTTP Delete Rest service with request body as payload
Hi All, My Integration server version is 9.12 and I have developed a HTTP DELETE Rest service for delete operation. Request for this...
Read more >Body handling for get and delete methods #68 - ladjs/frisbee
Currently Frisbee converts body into a query string for get and delete methods. That's weird because it's an artificial limitation and there ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
v3.0.0 is released which fixes this issue 🎉
npm install frisbee@latest
I’ve fixed this and it will be released in v3.0.0 later today.