Django + uwsgi + nginx + SSL

Question

I am using Django on DotCloud which uses Django on top of uwsgi + nginx. I am trying to redirect all http traffic to https which is leading to a redirect loop. I am using the following http configuration

if ($http_x_forwarded_port != 443) { rewrite ^ https://$http_host/; }

It seems that Django doesn't understand that it is operating on https and the header is not preserved. It redirects https://url.com/ to http://url.com/accounts/login/ which is redirecting again and again leading to a redirect loop. I am not really an expert in nginx and do not understand it well enough. What can I be doing wrong?

In short how do I run redirect http to https in django running on top of uswsgi and nginx.

try reading through this - yuji.wordpress.com/2008/08/15/… — Vidyanand
– Vidyanand, Commented Jul 21, 2011 at 23:09

sellonen · Accepted Answer · 2013-02-15 10:59:06Z

13

I needed a bit more to make Django aware that it should be using https.

In settings.py I added SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')

And in the nginx configuration

location / {
    proxy_set_header X-Forwarded-Proto https;
    include uwsgi_params;
    uwsgi_param UWSGI_SCHEME https;
    uwsgi_pass_header X_FORWARDED_PROTO;
    uwsgi_pass unix:///path/to/socket;
}

answered Feb 15, 2013 at 10:59

sellonen

1711 silver badge5 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

fmorency Over a year ago

For the sake of posterity, this answer works when only port 443 is open (ie. firewall blocks request on port 80)

raacer Over a year ago

uwsgi_pass_header allows to pass header from server to client, so this is probably not what you need here. What about correct redirects, the UWSGI_SCHEME param did the trick in my case without any custom headers. Is the SECURE_PROXY_SSL_HEADER setting really needed?

MechanisM · Accepted Answer · 2015-03-31 19:42:13Z

7

server {
  listen  80;
  server_name  yourhttphost;
  rewrite ^ https://yourhttpshost$request_uri? permanent; #301 redirect
}
server {
  listen 443;
  server_name  yourhttpshost;
  ........
  the rest
  ........
}

Using "if" in nginx config is a very bad idea!

edited Mar 31, 2015 at 19:42

answered Oct 8, 2011 at 10:24

MechanisM

9068 silver badges14 bronze badges

2 Comments

eficker Over a year ago

This is the correct answer as "if" statements are generally not a good idea in nginx configs.

MechanisM Over a year ago

Yep, I know about 'if' hehe

doomatel · Accepted Answer · 2011-08-22 11:17:52Z

3

if ( $scheme = "http" ) {
     rewrite ^/(.*)$   https://$host/ permanent;
}

answered Aug 22, 2011 at 11:17

doomatel

6771 gold badge7 silver badges8 bronze badges

1 Comment

kravietz Over a year ago

Having an "if" processed for each request is very ineffective in Nginx. It's better to create a separate :80 server and redirect every request hitting it.

Collectives™ on Stack Overflow

Django + uwsgi + nginx + SSL

3 Answers 3

2 Comments

2 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related