-
Notifications
You must be signed in to change notification settings - Fork 31
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
Support for Fly-Client-IP
?
#30
Comments
They do insert the client IP in X-Forwarded-For, but at the front, so it isn't returned by this library because of reasons described here #28 |
Have you tried configuring |
Adding headers: ["fly-client-ip"] works |
Thanks for confirming, @ivanpetrovic! I'll go ahead and close this issue, then. |
There's still a problem with socket connections where you need to use x headers. |
@bartblast What problem, specifically? I've never worked with Phoenix sockets.
If the |
Thanks for the thorough reply! Yes, I meant that x- headers only are passed in the Phoenix socket context. |
@bartblast Where did you find the |
@codeadict You need to use the IP listed in the fly.io admin panel: (your app) > Overview > IP addresses. Or analyze the actual request headers, it should be included there as well. |
This repo doesn't seem to work with Phoenix apps deployed to Fly.io, which is one of the larger Elixir webhosts. They instead provide a
[Fly-Client-IP](https://fly.io/docs/reference/runtime-environment/#fly-client-ip)
header. Would be cool if this project could support that, if possible.The text was updated successfully, but these errors were encountered: