Hey
@anrobinson01,
Yep youre right.....the current ReadyAPI! functionality doesnt include the ability to submit a GET request with a body because this essentially breaks the "rules" that are defined for http requests.
I cant remember the specific RFC numbers that describe http/http methods but theyre pretty clear.....an http request with a GET method does NOT include a payload (a body).
You could submit a new feature request to get this included in some time in the future in ReadyAPI! but i doubt this would ever be included in a future release cos GETs arent supposed to have a payload.
I am assuming your GET request Reads data as opposed to creating/updating data? (like an SQL's SELECT data retrieval).
Strictly speaking you could raise a defect on the interface design spec (the requirement that defines the API youre talking about), so that the erroneous requirement is updated to comply with RFC standards which would then require the code to be fixed. Either changing the method to maybe a POST method which supports a request payload or change the API so the the parameters you are currently defining in the request payload is instead handled by REST parameters on your request (most likely query parameters).
Ta
Rich
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
