I am maintaining a old .aspx
page in which all the data required by the page to show the content is passed in the URL of the GET
request as a part of query string. The result of this is that, as we keep on adding features, the URL keeps getting bigger.
I am thinking of shifting all the parameters from the query string to the Body of the GET
request.
Is it a good design decision and what is the use case of a body in GET
request?
Best Answer
GET requests with a body are supported in the HTML specs.
See the Stack Overflow question Is this statement correct? HTTP GET method always has no message body for a discussion.
However, it's unusual. You will surprise people with that solution. Simply switching to a POST is a better idea.
The only downside (upside?) is annoying RESTfulness acolytes.