We could add this in a 5.0, and maybe consider that this requires a specific flag to be set on the request.

Why a flag and not just an optional body parameter?

I've left an issue #1422 before finding this thread, I think all methods should be allowed to have a body if a user passes it in the request.

I'm struggling with the issue of a GET method with a body as well. After a while of digging on the internet, I found the answer on StackOverflow.

Refer to: https://stackoverflow.com/questions/978061/http-get-with-request-body#:~:text=The%20RFC2616%20referenced,was%20deleted

Years ago, it seems to be a bad practice to use body parameters for a GET request. However, now it should be an acceptable/valid practice for building a GET request like that. I just have a quick thought about an e-commerce website with many different types of filters (e.g.: brand, price range, category, seller name, etc.). Should it be more controllable if we have this kind of filter in a body?

As a back-end API dev, we can change it to a POST request. However, in my opinion, if I use a POST request, I want to change/update something in the database. And a GET method in the above example is exactly what I want to use.

I bet this "new" practice is relying on the evolving of data on the internet 😄

So, last but not least, hope that Dio can have this option in the next update.

Cheers!

If it works on postman, it should work on dio 😄

Many back-end API still do this use a body parameter for a GET request. Just encountered one that led me all the way here. The flexibility of having this is option in Dio is much welcomed