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
The request path api/Spaces-1/projects/Projects-45/refs%2fheads%2fdevelop/deploymentprocesses fails with 404 with keda http add-on in between. I believe this is because the escaped characters are unescaped in the forwarded request.
I get the same behaviour when i enable path rewriting in ingress.
Expected Behavior
Path not altered. Don't get a 404.
Actual Behavior
Path is altered, resulting in a 404.
Steps to Reproduce the Problem
Make a request with an escaped forward slash %2f and observe it forwarded as /
worldspawn
changed the title
Forwarded request paths appear to have escaped charcaters unescaped
Forwarded request paths appear to have escaped characters unescaped
Dec 22, 2023
worldspawn
changed the title
Forwarded request paths appear to have escaped characters unescaped
Forwarded request paths have escaped characters unescaped
Dec 22, 2023
Report
The request path
api/Spaces-1/projects/Projects-45/refs%2fheads%2fdevelop/deploymentprocesses
fails with 404 with keda http add-on in between. I believe this is because the escaped characters are unescaped in the forwarded request.I get the same behaviour when i enable path rewriting in ingress.
Expected Behavior
Path not altered. Don't get a 404.
Actual Behavior
Path is altered, resulting in a 404.
Steps to Reproduce the Problem
%2f
and observe it forwarded as/
Logs from KEDA HTTP operator
HTTP Add-on Version
0.6.0
Kubernetes Version
1.28
Platform
Microsoft Azure
Anything else?
No response
The text was updated successfully, but these errors were encountered: