Skip to content
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.

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

fix client IP checked against trusted proxies #379

Closed

Conversation

tuetenk0pp
Copy link

fixes #371

@tuetenk0pp tuetenk0pp marked this pull request as ready for review June 19, 2024 10:17
@tuetenk0pp
Copy link
Author

Just a note to the reviewer: I am completely new to both web-development and java script. That said, I tested the changes on my local docker / caddy / authentik stack and it worked as expected.

Copy link
Contributor

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the stale label Jul 20, 2024
@tuetenk0pp
Copy link
Author

This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

not yet ;-)

@MatissJanis
Copy link
Member

👋 Sorry for taking so long to review this PR!

cc @twk3 would you mind checking this one? It's changing some of the functionality introduced in #312 that you reviewed a while ago

@twk3
Copy link
Contributor

twk3 commented Jul 31, 2024

Closing for now based on the convo happening in #371 (comment)

But once we have the router trusted proxies in, we will want to revisit how this IP checking works as well.

@tuetenk0pp
Copy link
Author

@twk3 would you mind reopening this PR? #399 seems to be abandoned and this would at least fix the current issue.

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.

[Bug]: ACTUAL_TRUSTED_PROXIES has not desired effect
3 participants