From 3350cf7cfc3651dd8480f557fb5e36be66f72d84 Mon Sep 17 00:00:00 2001 From: cgourlay Date: Sat, 6 Mar 2021 20:04:07 +0000 Subject: [PATCH] Fix typos in the readme (#1061) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 80238649..776d9c78 100644 --- a/README.md +++ b/README.md @@ -90,7 +90,7 @@ Dozzle follows the [12-factor](https://12factor.net/) model. Configurations can
I installed Dozzle, but logs are slow or they never load. Help! - Dozzle uses Server Sent Events (SSE) which connects to a sever using a HTTP stream without closing the connection. If any proxy tries to buffer this connection, then Dozzle never receives the data and hangs forever waiting for the reverse proxy to flush the buffer. Since version `1.23.0`, Dozzle send the `X-Accel-Buffering: no` header which should stop reverse proxies buffering. However, some proxies may ignore this header. In those case, you need to explicitly disable any buffering. + Dozzle uses Server Sent Events (SSE) which connects to a server using a HTTP stream without closing the connection. If any proxy tries to buffer this connection, then Dozzle never receives the data and hangs forever waiting for the reverse proxy to flush the buffer. Since version `1.23.0`, Dozzle sends the `X-Accel-Buffering: no` header which should stop reverse proxies buffering. However, some proxies may ignore this header. In those cases, you need to explicitly disable any buffering. Below is an example with nginx and using `proxy_pass` to disable buffering.