Mock Service: mockRequest.requestContent is NULL (HTTP PUT)
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mock Service: mockRequest.requestContent is NULL (HTTP PUT)
mockRequest.requestContent is always NULL if PUT method is used although request is sent with some text in request body and Content-Length is set with appropriate value in HTTP headers.
If HTTP action is changed to POST then mockRequest.requestContent is populated correctly.
Is it a bug or do I miss something?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately, this is a bug. There is an internal defect of SOAP-2344 for this issue. This applies for the PUT and DELETE methods for a REST mock service.
Did my reply answer your question? Give Kudos or Accept it as a Solution to help others. ⬇️⬇️⬇️
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue with SoapUI 5.1.2 and 5.2.0.
I need to read the content of a PUT message.
Is a workaround exist for this issue ?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue with SoapUI 5.2.1 when I try to read the content of a PUT message.
Has this bug been fixed in any SOAP UI release ? Or is there a workaround for this issue ?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Anyone got the solution for this? Even I am seeing the same issue
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can anyone please suggest in which version this issue is resolved?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
i found one workaround for the problem. We are getting null output for mockRequest.getRequestContent() for PUT request
The workaround would be to use the following code
InputStream is = mockRequest.request.inputStream
BufferedReader br = new BufferedReader(new InputStreamReader(is, "UTF-8"));
StringBuilder sb = new StringBuilder()
while((s=br.readLine())!=null) {
sb.append(s)
}
String payLoad = sb.toString()
log.info payLoad
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The workaround works smoothly. However, if you need re-get the content down the road, you can't since the stream cannot be consumed twice. Hope there's a real solution from smartbear.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
NOT WORKS. I am using the ReadyAPI v 2.8.
I am unable to read request body.. So unable to return valid response to my Application under test = I am unable to test it = unable to use this tool for testing.
This topic is here sooo loooong.. And no solution? I am surprised. So nobody from SmartBear was working on it? It means, that we are paing for licenses, but no effect?
Please can somebody tell me, how to read POST body request ? because I must return some string value from it back to AUT..
