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
I'm thinking about using this middleware to replace some access rules that are currently on nginx. This seems like a good solution and I'd like to discuss the possibility of adding support for the X-Forwarded-For headers (or others) set by a proxy or load balancer in order to do the filtering.
In our case, our remoteAddress will always be the one of the reverse proxy, but it will send the actual client address in the mentioned header.
What do you think would be the best way to add support for that to this middleware? I can offer my help to make it happen, but I'm interested in what you think would be the best solution.
Let me know.
Cheers,
Lucas.
The text was updated successfully, but these errors were encountered:
My opinion was that another middleware should correct this. Messing with X-Forwarded-For is a bit sketchy if you don't do it right. Lemme see if I can either write one tonight, or find one that does what it should that I can recommend.
This middleware should work exactly like the nginx real_ip module if you're familiar with that.
Hey there!
I'm thinking about using this middleware to replace some access rules that are currently on nginx. This seems like a good solution and I'd like to discuss the possibility of adding support for the
X-Forwarded-For
headers (or others) set by a proxy or load balancer in order to do the filtering.In our case, our remoteAddress will always be the one of the reverse proxy, but it will send the actual client address in the mentioned header.
What do you think would be the best way to add support for that to this middleware? I can offer my help to make it happen, but I'm interested in what you think would be the best solution.
Let me know.
Cheers,
Lucas.
The text was updated successfully, but these errors were encountered: