You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could not find a solution in the existing issues, docs, nor discussions.
Describe the bug
Header matching happens in the error pipeline to select the required error handler. Unfortunately that process does not take case-insensitivity into account. That leads to wrong error handlers kicking in resulting in unexpected behavior.
How can the bug be reproduced
configure e.g. the following authenticator, unifier, error handlers and a default rule in the rules section:
start heimdall in the decision mode by making use of the above config
send curl requests to the decision endpoint by adding an Accept: text/plain header. The response will be 401 Unauthorized.
send curl requests to the decision endpoint by adding an accept: text/plain header. The response will be a 302 with a the location header set to the configured url.
For both requests redirect is expected.
Relevant log output
No response
Relevant configuration
No response
Version
0.6.0-alpha
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Preflight checklist
Describe the bug
Header matching happens in the error pipeline to select the required error handler. Unfortunately that process does not take case-insensitivity into account. That leads to wrong error handlers kicking in resulting in unexpected behavior.
How can the bug be reproduced
Accept: text/plain
header. The response will be 401 Unauthorized.accept: text/plain
header. The response will be a 302 with a the location header set to the configured url.For both requests redirect is expected.
Relevant log output
No response
Relevant configuration
No response
Version
0.6.0-alpha
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: