Ok, this seems related to the specific use of localhost. If I try it with
any other domain name, it works as expected.
I'm still interested in an answer for my own learning, but it's definitely
lower priority now.
Il giorno lun 17 dic 2018 alle ore 01:10 Gianluigi Zanettini
ha scritto:
> Hi gu
Hello!
On Sun, Dec 16, 2018 at 02:45:56PM -0800, Chad Phillips wrote:
> I use software that runs a speed test via websockets. When proxying this
> websocket connection through Nginx, the 'download' portion of the test is
> inaccurate.
>
> My theory is that this is due to Nginx buffering the resp
Hi guys,
I'm testing my config on localhost with nginx/1.15.7 before deploying.
Since I only want to handle specific hostnames, I setup a catch-default:
server {
listen 443 ssl default_server;
...
return 400;
}
Then I setup my real config:
server {
server_name localhost;
root /usr/share/n
I use software that runs a speed test via websockets. When proxying this
websocket connection through Nginx, the 'download' portion of the test is
inaccurate.
My theory is that this is due to Nginx buffering the response from the
backend server, thus the timer on the backend server reports an inac
