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.

Sign up for GitHub

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

Jump to bottom

Encoded urls are not handled properly #29357

Open

lgblaumeiser opened this issue Jan 15, 2025 · 0 comments

lgblaumeiser commented Jan 15, 2025

Describe the bug
Observed in vault version 1.18.1, not observed with version 1.16.1 where this works as expected

To Reproduce
Steps to reproduce the behavior:

Run the following rest call: "https://server-url/v1%2Fauth%2Ftoken%2Flookup-self"
Observe that not the requested json information is returned but a redirect message with html body

Expected behavior
The same information returned as if the call would be "https://server-url/v1/auth/token/lookup-self"

Environment:
Based on helm chart 0.29.0 in a Kind Kubernetes cluster

Vault server configuration file(s):
nothing special, is only set up in a test environment, but in dev mode

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment