Skip to content

fix: use X-Forwarded-Uri if it exists for pathRegex match - #8

Closed
deb-hacktron wants to merge 3 commits into
base/pr-2192from
fix-use-x-forwarded-uri-for-pathregex-match
Closed

fix: use X-Forwarded-Uri if it exists for pathRegex match#8
deb-hacktron wants to merge 3 commits into
base/pr-2192from
fix-use-x-forwarded-uri-for-pathregex-match

Conversation

@deb-hacktron

Copy link
Copy Markdown
Owner

Fresh PR to rerun Hacktron after pipeline changes.

demo-bot added 3 commits April 22, 2026 14:42
the functions `isApiPath` and `isAllowedPath` use the `req.URL.Path` property which leads to faulty behavior when behind a reverse proxy. The correct path can be inferred from the `X-Forwarded-Uri` header by making use of the already provided `requestutil.GetRequestURI` function.
@deb-hacktron

Copy link
Copy Markdown
Owner Author

Refreshing scan with a new PR.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant