Need SSL state to be visible behind a double nginx proxy
lists at ruby-forum.com
Thu Oct 30 22:05:17 MSK 2008
I am not sure if you can use the port in the server_name directive. I
think you need to add listen directives.
Note i could be totally off on this but this is a very very simplistic
view of what i was trying to accomplish
Basically demo'ing 3 different server configs with 2 being your
"frontend" server's for doing SSL and then having 1 server listening on
two ports and manually setting the protocal no the second when it is
passed onto rails.
Nick Pearson wrote:
> Hi Rob,
> Thank you very much for the suggestions. The first one isn't really an
> option due to the caching that the CMS does (not, that is, without some
> serious rework regarding how the cached files are written and deleted).
> However, your second solution has a lot of promise. I do have one
> on it, though.
> Because of the caching, each site that runs on my CMS has its own nginx
> config file, each with two server directives -- one for http and one for
> https. Using your solution, this would remain the same, except that
> of listening for port 443, the https server directive would listen on
> other port. My initial tests show that I can use this for one server
> directive (the http one):
> server_name: www.domain.com;
> and this for the other (the https one):
> server_name: www.domain.com:1234;
> I can't find any documentation or examples that say whether specifying a
> port with the host name in a server_name directive is valid. I'll need
> do some more testing to be sure it works as I believe it does. Do you
> if this usage of host:port is valid for server_name? If so, then I
> your second solution will solve my problem. Thanks!
Posted via http://www.ruby-forum.com/.
More information about the nginx