Yeah
@rao's right...http rules (check out w3.org or similar) define a GET as a data retrieval based on parameters included in the URI and query string and so shouldn't include a payload.
I have worked on a project when a POST method was misused for data retrieval (i.e. instead of using a GET method) and i have worked on a project when a GET did include a payload...., but both these were due to devs not knowing what they're doing and no code reviews in place and got them sorted once i'd raised defects on them.
If you consider most REST clients, they don't even include the facility to submit a payload in a GET request.
I'd double check the technical requirements and if they are misusing an http method, i'd go back to the devs and point them to any solution or technical architect....they would never allow this.
Cheers,
richie
if this helped answer the post, could you please mark it as 'solved'? Also if you consider whether the title of your post is relevant? Perhaps if the post is solved, it might make sense to update the Subject header field of the post to something more descriptive? This will help people when searching for problems. Ta
