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
Would it be desirable to add a podinfo endpoint that accepts dynamic paths?
For example, pattern /echo/** would accept /echo, /echo/foo, echo/foo/bar, etc. All paths would be handled the same way.
For now, I'm using k8s echoserver (registry.k8s.io/e2e-test-images/echoserver:2.5) to test this, as it always responds the same way for any URI path.
I use this feature to test arbitrary path patterns passed through a reverse proxy.
The text was updated successfully, but these errors were encountered:
Yes dynamic paths for echo would be great!
echo
Sorry, something went wrong.
@stefanprodan I've opened #271 to address this. Take a look and let me know what you think.
@stefanprodan @merusso since the PR for this feature has been merged, can we close this issue?
Ah yes, forgot to close it, thanks for the reminder.
No branches or pull requests
Would it be desirable to add a podinfo endpoint that accepts dynamic paths?
For example, pattern /echo/** would accept /echo, /echo/foo, echo/foo/bar, etc. All paths would be handled the same way.
For now, I'm using k8s echoserver (registry.k8s.io/e2e-test-images/echoserver:2.5) to test this, as it always responds the same way for any URI path.
I use this feature to test arbitrary path patterns passed through a reverse proxy.
The text was updated successfully, but these errors were encountered: