Hi Nick,<br> Why don't you simplify your setup. You can have your Rails App running on your big server without needing nginx on it at all. All you do is open up the rails instances to allow access from your nginx frontends and then proxy the requests to it. Instead of having to proxy to nginx and then proxying again. <br>
<br> Or the other option you can do is on your nginx server that proxy's to your rails app. Have 2 server directives that listen on two different ports. Then when non-ssl traffic comes into your frontend server and redirect it to server 1, which has your standard proxy_pass. Then on your frontends have your ssl portion of the server redirect to the 2nd server port on the backend that sets the X_FORWARDED_PROTO to https manually.<br>
<br>Rob<br><br><div class="gmail_quote">On Wed, Oct 29, 2008 at 3:14 PM, Nick Pearson <span dir="ltr"><<a href="mailto:nick.pearson@gmail.com">nick.pearson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I have what I think is an obscure problem to which I cannot find a<br>
solution in the nginx docs. Here's a summary of the problem:<br>
<br>
I have a content management system that I wrote (using Rails), and it<br>
hosts several sites. Each site has SSL, and due to a policy limit by<br>
my hosting provider, each virtual server ("slice") can only have five<br>
external IP addresses. This creates a problem in that the CMS that<br>
was built to host lots of sites is limited to hosting only five. My<br>
solution was to set up smaller slices in front of the main server, and<br>
the small slices would run nothing but nginx. As such, the<br>
"front-end" nginx instances would proxy requests to the "back-end"<br>
nginx, and the "back-end" nginx would proxy requests through to the<br>
Rails app server instances.<br>
<br>
I saw a recent post on SSL pass-through, but this is not what I'm<br>
looking for. As the slices are on the same network at my hosting<br>
provider, I don't care that the slice-to-slice communications are<br>
encrypted. This is not an issue.<br>
<br>
What is an issue is that the application (and thus the Rails app<br>
server instances) need to be able to determine whether a request came<br>
in using SSL or not. Because requests are proxied through two<br>
instances of nginx running on separate slices, the back-end nginx<br>
cannot see whether a request came in over http or https -- because<br>
either way, the request arrived at the back-end nginx over http (not<br>
https). Here is a simple depiction of two requests -- one over http<br>
and one over https:<br>
<br>
client ---http---> nginx ---http---> nginx ---> rails<br>
client ---https--> nginx ---http---> nginx ---> rails<br>
<br>
As you can see, it is the second (back-end) nginx instance in the<br>
chain that tells the Rails app server instances whether the request<br>
made to nginx was over http or https. And since all requests to the<br>
second nginx instance are made over http, it passes this on to the<br>
Rails app, which thinks all requests are made over http even if the<br>
communication between the client and the first (front-end) nginx is<br>
over https.<br>
<br>
Also worth noting is that there are no SSL errors. If the request is<br>
made over http, it works. And if the request is made over https, it<br>
works. The app server just doesn't know whether a request was made<br>
over http or https.<br>
<br>
I attempted to set the following on the back-end nginx:<br>
<br>
proxy_set_header X_FORWARDED_PROTO $scheme;<br>
<br>
but not surprisingly, it doesn't work. ($scheme is either "http" or<br>
"https", taken directly from the request.) I may have a solution to<br>
the problem, but it will require some extra plumbing work in Rails to<br>
make it functional. What I am able to do is to set a custom header<br>
and then read the value of that header in the Rails code. Here is<br>
what I've tried:<br>
<br>
proxy_set_header HTTPS on;<br>
<br>
Then, in the Rails code, I can look for the HTTP_HTTPS environment<br>
variable. (nginx apparently prepends anything sent to<br>
proxy_set_header with "HTTP_".) While this solution will probably<br>
work, I would prefer to have nginx pass the request scheme to the app<br>
servers without having to change the internals of Rails (by rewriting<br>
the request.ssl? method).<br>
<br>
This could be accomplished if nginx would let me conditionally set a<br>
header based on the value of another header. I just can't figure out<br>
how to read a header. Here's what I would like to do -- keep the<br>
"proxy_set_header HTTPS on;" (above) on the front-end nginx and use<br>
the header on the back-end nginx -- like this:<br>
<br>
if ($HTTP_HTTPS = on) {<br>
proxy_set_header X_FORWARDED_PROTO https;<br>
}<br>
<br>
I realize that this means that anyone could arbitrarily add this<br>
header to a request and trick the Rails server into thinking the<br>
request was secure when it was not, but I would solve this by setting<br>
"ignore_invalid_headers on;" or similar on the front-end nginx.<br>
<br>
Can anyone tell me whether it is possible to read custom headers and<br>
to act on them as in my example above? If not, I think this would be<br>
a great addition.<br>
<br>
Thanks in advance.<br>
<font color="#888888"><br>
Nick Pearson<br>
<br>
</font></blockquote></div><br>