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
When using a HTTP proxy, client's IP address is usually obtained from X-Forwarded-For that is set by proxy. With uWSGI the address is passed by proxy (nginx) as REMOTE_ADDR and REMOTE_PORT params, but there does not seem to be a way to access it and the REMOTE_ADDR and REMOTE_PORT received by the WSGI app point to proxy (or nothing if a unix socket is used).
Do I have to add X-Forwarded-For even with uWSGI? The docs don't mention it, so one would think that the basic configuration should be enough.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using a HTTP proxy, client's IP address is usually obtained from
X-Forwarded-Forthat is set by proxy. With uWSGI the address is passed by proxy (nginx) asREMOTE_ADDRandREMOTE_PORTparams, but there does not seem to be a way to access it and theREMOTE_ADDRandREMOTE_PORTreceived by the WSGI app point to proxy (or nothing if a unix socket is used).Do I have to add
X-Forwarded-Foreven with uWSGI? The docs don't mention it, so one would think that the basic configuration should be enough.Beta Was this translation helpful? Give feedback.
All reactions