Wow! That's it! Thank you, Francis!
I need to catch up with some reading on http//2.0. I didn't know that
"Connection Upgrade" is http/1.1 specific.
So, in order to set up the websocket anyway and keep http/2.0 (don't know
how much sense that makes) there would be 2 options as I see it:
1. Stati
On Tue, Jul 20, 2021 at 12:39:51PM +0200, Dorin RuV wrote:
Hi there,
> I'm currently having an issue with nginx which I cannot get to the bottom
> of.
> server{
> listen 443 ssl http2;
Does anything change if you just remove that "http2"?
> location / {
> proxy_http_version 1.1;
>
Hi Sergey,
Thank you for lending a hand!
I have enabled debug and here are two different calls to the backend:
1. It worked (The nginx config contains a hard-coded "Connection Upgrade"
and "Upgrade Websocket" proxy_set_headers)
"2021/07/21 13:36:43 [debug] 1#1: bind() 0.0.0.0:8060 #6
2021/07/21
Hi Dorin,
hope you're doing well.
On Tue, Jul 20, 2021 at 12:39:51PM +0200, Dorin RuV wrote:
> Hi everybody,
>
> I'm currently having an issue with nginx which I cannot get to the bottom
> of.
>
> I'm using nginx as a reverse proxy/load balancer in front of Kubernetes.
> I'm trying to set up We
Hi everybody,
I'm currently having an issue with nginx which I cannot get to the bottom
of.
I'm using nginx as a reverse proxy/load balancer in front of Kubernetes.
I'm trying to set up Websocket connections with an app running in
Kubernetes, but there are some problems. I have followed the "more
