Can somebody explain more about why you are "not supposed to" proxy to https
backend?

Are you saying because it does not buy you anything since Nginx terminates
the SSL protocol?

On Sun, Apr 17, 2011 at 3:39 AM, Edho P Arief <edhoprima@gmail.com> wrote:

> On Sun, Apr 17, 2011 at 2:24 PM, speedfirst <nginx-forum@nginx.us> wrote:
> > I have this requirement. I want to use nginx as the reverse proxy, which
> > listen on address A and forward the request to the backend server with
> > address B. However, if B is down, I want the request to be sent to
> > address C. The question is, address B is https and address C is http.
> > But for the argument of proxy_pass module, I can only write one prefix
> > (either "http" or "https").
> >
>
> you're not supposed to proxy to https backend. And I don't know how
> mixed environment like that would work anyway. If the client isn't
> using SSL then what's the point. But then if it's SSL then who
> supposed to give out the certificate.
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx