Thank you for your reply, Roman.
It turns out the issue was adding the various proxy and forwarded headers
in that entry. Changing it to the below block fixed my issue:
#send to non-websocket process
location / {
proxy_pass http://localhost:8082;
proxy_set_header Host $host;
Hello Joseph,
On Wed, Aug 22, 2018 at 10:24:23AM -0400, Joseph Wonesh wrote:
> Hello,
>
> I am trying to route requests such that those requiring websockets will
> route to a long-lived nginx process, and all others will go to the general
> reverse-proxy which handles all other traffic. These ngi
Hello,
I am trying to route requests such that those requiring websockets will
route to a long-lived nginx process, and all others will go to the general
reverse-proxy which handles all other traffic. These nginx processes exist
in our AWS cloud behind an ELB that has been configured to use Proxy
