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
No response
Hi Ory Team
I guess the access rules of Ory Oathkeeper do not support X-Forwarded-* headers properly.
Steps to reproduce a bug with x-forwarded headers
curl -v -H "X-Forwarded-Host: dev.pp" -H "X-Forwarded-Proto: http" -H "x-forwarded-port: 4455" http://localhost:4455/header
Actual result:
404 Not Found
Expected result:
200 OK { "args": {}, "data": "", "files": {}, "form": {}, "headers": { "Accept": "/", "Accept-Encoding": "gzip", "Host": "dev.pp", "User-Agent": "curl/7.68.0", "X-Amzn-Trace-Id": "Root=1-654d02aa-1ed22ecf2a4623d66ae70ac3" }, "json": null, "method": "GET", "origin": "91.215.139.68", "url": "https://dev.pp/anything/header" }
While, request with Host header works like a charm:
Host
curl -v -H "Host: dev.pp:4455" http://localhost:4455/header
Response:
200 OK { "args": {}, "data": "", "files": {}, "form": {}, "headers": { "Accept": "*/*", "Accept-Encoding": "gzip", "Host": "dev.pp", "User-Agent": "curl/7.68.0", "X-Amzn-Trace-Id": "Root=1-654d0c78-4f0df818446962ab50e760ab" }, "json": null, "method": "GET", "origin": "91.215.139.68", "url": "https://dev.pp/anything/header" }
log: level: debug format: json serve: proxy: trust_forwarded_headers: true errors: fallback: - json handlers: json: enabled: true config: verbose: true access_rules: matching_strategy: glob repositories: - file:///etc/config/oathkeeper/access-rules.yml authenticators: anonymous: enabled: true config: subject: guest noop: enabled: true authorizers: allow: enabled: true mutators: noop: enabled: true
0.40.6
Linux
Docker Compose
The text was updated successfully, but these errors were encountered:
Same issue here with v0.40.7! Ory ppl, i am happy to send logs
@eratolekov have you been able to sort this out on your end?
Sorry, something went wrong.
nope
No branches or pull requests
Preflight checklist
Ory Network Project
No response
Describe the bug
Hi Ory Team
I guess the access rules of Ory Oathkeeper do not support X-Forwarded-* headers properly.
Reproducing the bug
Steps to reproduce a bug with x-forwarded headers
Actual result:
Expected result:
While, request with
Host
header works like a charm:Response:
Relevant log output
No response
Relevant configuration
Version
0.40.6
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker Compose
Additional Context
No response
The text was updated successfully, but these errors were encountered: