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

Response codes triggered by url params #23

Open
hoda0013 opened this issue Nov 24, 2015 · 1 comment
Open

Response codes triggered by url params #23

hoda0013 opened this issue Nov 24, 2015 · 1 comment
Labels

Comments

@hoda0013
Copy link

Is there a way for the route to respond with a certain response code without needing to add a url parameter to induce the response code?

For example, if I have a route called /session, and I want to get a 200 response then I call base_url/session and if I have everything setup correctly I get a 200 response.

However, if I call the same route but want to get a 201 response instead, it seems that I am forced to call base_url/session?__statusCode=201

For my specific test case I can't change the url params on the fly so I'd prefer to have my client try to access the same route with the same params every time and be able to manipulate the server response rather than needing to induce a certain server response using params.

Does that make sense? Is it possible that this tool can be used in the way I've described?

@engFelipeMonteiro
Copy link

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants