Merging upstream version 1.39.0.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

1 files changed, 21 insertions, 12 deletions

diff --git a/docs/Running-behind-nginx.md b/docs/Running-behind-nginx.md
index a94f4058d..842a9c326 100644
--- a/docs/Running-behind-nginx.md
+++ b/docs/Running-behind-nginx.md
@@ -1,12 +1,3 @@
-<!--
-title: "Running Netdata behind Nginx"
-custom_edit_url: "https://github.com/netdata/netdata/edit/master/docs/Running-behind-nginx.md"
-sidebar_label: "Running Netdata behind Nginx"
-learn_status: "Published"
-learn_topic_type: "Tasks"
-learn_rel_path: "Setup/Expose local dashboard through proxy"
--->
-
 # Running Netdata behind Nginx
 
 ## Intro
@@ -51,7 +42,7 @@ With this method instead of `SERVER_IP_ADDRESS:19999`, the Netdata dashboard can
 upstream backend {
     # the Netdata server
     server 127.0.0.1:19999;
-    keepalive 64;
+    keepalive 1024;
 }
 
 server {
@@ -216,8 +207,6 @@ If your Nginx is on `localhost`, you can use this to protect your Netdata:
     bind to = 127.0.0.1 ::1
 ```
 
-
-
 You can also use a unix domain socket. This will also provide a faster route between Nginx and Netdata:
 
 ```
@@ -259,6 +248,26 @@ Nginx logs accesses and Netdata logs them too. You can prevent Netdata from gene
       access log = none
 ```
 
+## Use gzip compression
+
+By default, netdata compresses its responses. You can have nginx do that instead, with the following options in the `location /` block:
+
+```conf
+  location / {
+		...
+		gzip on;
+		gzip_proxied any;
+		gzip_types *;
+	}
+```
+
+To disable Netdata's gzip compression, open `netdata.conf` and in the `[web]` section put:
+
+```conf
+[web]
+    enable gzip compression = no
+```
+
 ## SELinux
 
 If you get an 502 Bad Gateway error you might check your Nginx error log: