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

Provide warning feedback about response status rule #46

Open
matejdro opened this issue Jul 1, 2021 · 4 comments
Open

Provide warning feedback about response status rule #46

matejdro opened this issue Jul 1, 2021 · 4 comments
Labels
enhancement New feature or request

Comments

@matejdro
Copy link

matejdro commented Jul 1, 2021

When attempting to rewrite response status like that:

image

nothing happens. Rewriting response status only seem to work when match is filled out (for example with "404"). This is inconsistent with all other rewrite types where blank field acts as a wildcard match that matches everything.

@NicolaVerbeeck
Copy link
Contributor

That's because the value is invalid. It should be '200 OK'. You need to fill in the full value of the status. There should be a warning message generated when trying to replace

@matejdro
Copy link
Author

matejdro commented Jul 1, 2021

Huh, why does this work then, though?

image

@NicolaVerbeeck
Copy link
Contributor

Because it will only replace the '404' part from the '404 Not Found' line -> '200 Not Found'

@matejdro
Copy link
Author

matejdro commented Jul 2, 2021

I see. Thanks for the explanation. Maybe this ticket could be changed into a feature request, that required format of the value is explained in the UI?

@NicolaVerbeeck NicolaVerbeeck changed the title Response status does not work when Match field is blank Provide warning feedback about response status rule Jul 2, 2021
@NicolaVerbeeck NicolaVerbeeck added the enhancement New feature or request label Jul 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants