For a server {} that you want to make both universally compatible with both
http port 80 and https port 443 ssl requests.
This was my solution for my own sites.
#inside http block
upstream proxy_web_rack { #port 80 unsecured requests
server 172.16.0.1:80;
}
upstream proxy_web_rack_ssl { #port 443
*Gesendet:* Mittwoch, 22. Februar 2017 18:52:00
> *An:* nginx ML
> *Cc:* B.R.
> *Betreff:* Re: Nginx multiple upstream with different protocols
>
> I suggest you proxy traffic to an upstream group, and then use
> failure/timeout parameters there with proper tuning to retry request
h, 22. Februar 2017 15:58:26
An: nginx@nginx.org<mailto:nginx@nginx.org>
Betreff: RE: Nginx multiple upstream with different protocols
If you are SSL on the frontend (server directive) why would you want to proxy
between ssl/non-ssl on the upstreams? Can they not be the same? I don'
* nginx [mailto:nginx-boun...@nginx.org] *On Behalf Of *Kilian Ries
> *Sent:* Wednesday, February 22, 2017 9:55 AM
> *To:* nginx@nginx.org
> *Subject:* Nginx multiple upstream with different protocols
>
>
>
> Hi,
>
>
>
> i'm trying to setup two Nginx upstreams (one w
ric S
Gesendet: Mittwoch, 22. Februar 2017 15:58:26
An: nginx@nginx.org
Betreff: RE: Nginx multiple upstream with different protocols
If you are SSL on the frontend (server directive) why would you want to proxy
between ssl/non-ssl on the upstreams? Can they not be the same? I don't get
wh
9:55 AM
To: nginx@nginx.org
Subject: Nginx multiple upstream with different protocols
Hi,
i'm trying to setup two Nginx upstreams (one with HTTP and one with HTTPS) and
the proxy_pass module should decide which of the upstreams is serving "valid"
content.
The config s
Hi,
i'm trying to setup two Nginx upstreams (one with HTTP and one with HTTPS) and
the proxy_pass module should decide which of the upstreams is serving "valid"
content.
The config should look like this:
upstream proxy_backend {
server xxx.xx.188.53;
server xxx.xx.188.53:4
