Use in programming (Python / Django) a method HttpRequest.get_host () (# https://docs.djangoproject.com/en/dev/r ... -response/ django.http.HttpRequest.get_host) but this method fails when the host is behind multiple proxies. In my application redirect some subdomains for her, and through the method mentioned recognize the subdomain in question.

Normally operates. The former method get the URI. (like [url]classificados.fatimanews.com.br[/url], [url]classificados.bonitoinforma.com.br[/url]) but today I created a subdomain ([url]classificados.portalaguasclaras.com.br[/url]), pointed to the IP of the machine, as I always do, and it happens that this time the method returns the IP of the machine and not the URL for me to identify it.

I use nginx. What would it take? Could you help me?

I don't know which HTTP header exactly Django recognizes, I use Pyramid. And for that I set a combination of:

proxy_set_header Host $host;
proxy_set_header X-Real-Ip $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

or if you run Django under uwsgi, it's uwsgi_pass_header, etc... See nginx docs for more info on that.

I tried that and it did not work

uwsgi_pass_header Host;
proxy_set_header Host $http_host;
proxy_pass_header Host;

What I doing wrong? I really need it.

Thanks man for any help.

This is what I pass when using uwsgi

uwsgi_param QUERY_STRING $query_string;
uwsgi_param REQUEST_METHOD $request_method;
uwsgi_param CONTENT_TYPE $content_type;
uwsgi_param CONTENT_LENGTH $content_length;

uwsgi_param REQUEST_URI $request_uri;
uwsgi_param PATH_INFO $document_uri;
uwsgi_param DOCUMENT_ROOT $document_root;
uwsgi_param SERVER_PROTOCOL $server_protocol;

uwsgi_param REMOTE_ADDR $remote_addr;
uwsgi_param REMOTE_PORT $remote_port;
uwsgi_param SERVER_PORT $server_port;
uwsgi_param SERVER_NAME $server_name;

You probably want the bottom one.

_________________
Paid support
How to ask for help
1. Give details of your problem
2. Post any errors
3. Post relevant logs.
4. Don't hide details i.e. your domain, it just makes things harder
5. Be polite or you'll be eaten by a grue

I already use these settings.

It's not working,

I'm almost giving up a vps. :/

You're mixing uwsgi and proxy pass. which is it? uwsgi or proxy?

Sorry, but I do not know what I want. I do not know is if I want uwgi or proxies.
I just want to resolve the error of the initial question.

I can not get the URL when using the HttpRequest.get_host () in Django / Python in some cases. Usually works, but in some cases, instead of receiving the URL, IP comes.

My specialty is not servers.

Excuse my ignorance.

If you paste your config file here, it will be quite useful for figuring out what your configuration is.

_________________

/* TODO: need to add signature to posts */

my current settgins

location / {
uwsgi_pass djangoapp_skalist;

uwsgi_param CONTENT_TYPE $content_type;
uwsgi_param CONTENT_LENGTH $content_length;

uwsgi_param REQUEST_URI $request_uri;
uwsgi_param PATH_INFO $document_uri;
uwsgi_param DOCUMENT_ROOT $document_root;
uwsgi_param SERVER_PROTOCOL $server_protocol;

uwsgi_param REMOTE_ADDR $remote_addr;
uwsgi_param REMOTE_PORT $remote_port;
uwsgi_param SERVER_PORT $server_port;
uwsgi_param SERVER_NAME $server_name;

}

You are using uWSGI.

In my world, we use gunicorn (and therefore HTTP instead of uWSGI) and our front-end proxies pass the remote IP address in the X-Real-IP header, so we just proxy_pass_header X-Real-IP. So, I'm mostly guessing here. You'll probably need to do something like this:

uwsgi_param REMOTE_ADDR $http_x_real_ip;

Things will be different if your front-end isn't passing you X-Real-IP.

My google-fu was failing out on finding an example of uWSGI+nginx+X-Real-IP, unfortunately, so your mileage may vary. This is, in part, why I use gunicorn.

_________________

/* TODO: need to add signature to posts */