Re: forward 443 requests to correct (?) port

On Mon, Sep 19, 2022 at 12:25:04PM -0600, Brian Carey wrote: Hi there, > Maybe I'm misunderstanding how this should work. Can I use non-ssl > connections for upstream servers when the originating request is https? >From nginx's point of view: yes, not a problem. >From the upstream application's

Re: Fwd: soooo close: nginx gunicorn flask directory stripped from links

On Fri, Sep 16, 2022 at 12:11:05PM -0600, Brian Carey wrote: Hi there, > OK, sadly I was pre-mature in my explanation and claim of success, although > the trailing slash was clearly an issue. Now I can use the application fine > in the open browser  which I can see did implement my changes becaus

Re: forward 443 requests to correct (?) port

It doesn't work if the originating url is https:// but does if it is http:// On 9/19/22 12:46, Eric Germann via nginx wrote: Do you have https: at the front of the URL instead of http:? --- Eric Germann ekgermann {at} semperen {dot} com || ekgermann {at} gmail {dot} com LinkedIn: https://www.l

Re: forward 443 requests to correct (?) port

Do you have https: at the front of the URL instead of http:? --- Eric Germann ekgermann {at} semperen {dot} com || ekgermann {at} gmail {dot} com LinkedIn: https://www.linkedin.com/in/ericgermann Medium: https://ekgermann.medium.com

forward 443 requests to correct (?) port

Hi, Maybe I'm misunderstanding how this should work. Can I use non-ssl connections for upstream servers when the originating request is https? I'm forwarding nginx requests to an apache server listening on 8080. Everything works fine if I explicitly use http but not https. My nginx site itse