13 messages in ru.sysoev.nginxRe: Need SSL state to be visible behi...
FromSent OnAttachments
Nick PearsonOct 29, 2008 1:14 pm 
Nick PearsonOct 29, 2008 2:26 pm 
Rob SchultzOct 29, 2008 5:26 pm 
Nick PearsonOct 29, 2008 9:11 pm 
Rob SchultzOct 30, 2008 12:04 pm 
Nick PearsonOct 30, 2008 1:29 pm 
Almir KaricOct 30, 2008 2:19 pm 
Rob SchultzOct 30, 2008 2:39 pm 
Nick PearsonOct 30, 2008 2:41 pm 
Nick PearsonOct 30, 2008 3:05 pm 
Nick PearsonNov 6, 2008 6:25 am 
Dave CheneyNov 6, 2008 12:50 pm 
Nick PearsonNov 6, 2008 1:05 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Need SSL state to be visible behind a double nginx proxyActions...
From:Nick Pearson (nick@gmail.com)
Date:Nov 6, 2008 1:05:54 pm
List:ru.sysoev.nginx

You're right that using "proxy_set_header X_FORWARDED_PROTO https;" is all that's needed to tell Rails that the request is secure. Your back-end server configs are what I used. The reason for listening on multiple ports is that the back-end nginx does not pass the X_FORWARDED_PROTO header (from the front-end nginx) through to Rails.

I'm not quite clear on which part isn't necessary, though. Your example config is essentially what I'm using now.

Thanks, Nick