Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting incorrect response when we are having two rrpairs #595

Open
pkotha5 opened this issue Jan 9, 2020 · 1 comment
Open

Getting incorrect response when we are having two rrpairs #595

pkotha5 opened this issue Jan 9, 2020 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@pkotha5
Copy link

pkotha5 commented Jan 9, 2020

Steps : 1. Create a service with two RR Pairs(1st RRpair : Request payload is blank, Response Payload is valid response , 2nd RR Pair : valid Request Payload, Response Payload) for the POST methods
2.Service created successfully.
3. Open any REST Client/Test Service functionality and give 2nd Request payload.

Actual Result : Getting 1st request response payload instead of 2nd request response payload.
1
2
3

@pkotha5 pkotha5 added the bug Something isn't working label Jan 9, 2020
@Pradeep298
Copy link
Contributor

Pradeep298 commented Jan 9, 2020

I analysed it more. If there is no payload (req body) then GET HTTP method is perfect. So in this case if you set first request as Get HTTP request, you would not face this issue.

Also suppose there is a test case where you make 2 or 3 HTTP Get request. First with normal GET request without body and others is with request body. You would always get response from first request(without req. body) only. This is because It doesn't matter whether you set a req. body with Get request or you don't set any body. Both are equal. This will behave as duplicate request internally. That is why Get request is not meant to have a body and if you need a req. body use post method there. OR if you are not using any req. body then always use a GET method.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants