Hello!
On Tue, Dec 18, 2018 at 11:58:49AM -0500, thehunmonkgroup wrote:
> I could deal with *some* inaccuracy, but the results are completely out of
> whack. Downloading 256KB of data via the websocket over a poor DSL
> connection happens near instantaneously from the websocket server's point of
I could deal with *some* inaccuracy, but the results are completely out of
whack. Downloading 256KB of data via the websocket over a poor DSL
connection happens near instantaneously from the websocket server's point of
view, which to me indicates that Nginx is consuming all that data in a
buffer in
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
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
