We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When setting WireTap as a validation proxy , it would be nice to return as well the error details to the client and not only the 502
could be returning HTTP RFC problem format or whaterver
meanning instead of empty payload returning something like to have better understanding as well from client point of view.
it should include response violation as well as type and how to fix
(i know all those are in the UI but having them as well in the return would help the debugging lifecycle.
The text was updated successfully, but these errors were encountered:
This is a good idea.
Sorry, something went wrong.
No branches or pull requests
When setting WireTap as a validation proxy , it would be nice to return as well the error details to the client and not only the 502
could be returning HTTP RFC problem format or whaterver
meanning instead of empty payload returning something like to have better understanding as well from client point of view.
it should include response violation as well as type and how to fix
(i know all those are in the UI but having them as well in the return would help the debugging lifecycle.
The text was updated successfully, but these errors were encountered: