README.md | 48 +++++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 43 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index a6b2776..5d1c90f 100644
--- a/README.md
+++ b/README.md
@@ -29,13 +29,44 @@ There is no detailed documentation about BigPipe yet, but all of the following d
 - <https://www.drupal.org/documentation/modules/dynamic_page_cache>
 - <https://www.facebook.com/notes/facebook-engineering/bigpipe-pipelining-web-pages-for-high-performance/389414033919>
 
-## Varnish
+
+
+---
+
+
+
+# Environment requirements
 
 - BigPipe uses streaming, this means any proxy in between should not buffer the response: the origin needs to stream directly to the end user.
-- Hence Varnish should not buffer the response, or otherwise the end result is still a single flush, which means worse performance again.
+- Hence the web server and any proxies should not buffer the response, or otherwise the end result is still a single flush, which means worse performance again.
 - BigPipe responses contain the header `Surrogate-Control: no-store, content="BigPipe/1.0"`.
 
-Therefore the following VCL makes Varnish compatible with BigPipe:
+
+## Apache
+
+When using Apache, there is nothing to do: no buffering by default.
+
+
+## FastCGI
+
+When using FastCGI, you must disable its buffering.
+
+- When using Apache+FastCGI, [set `FcgidOutputBufferSize` to `0`](https://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html#fcgidoutputbuffersize):
+```
+<IfModule mod_fcgid.c>
+  FcgidOutputBufferSize 0
+</IfModule>
+```
+- When using Nginx+FastCGI, [set `fastcgi_buffering` to `off`](http://nginx.org/en/docs/http/ngx_http_fastcgi_module.html#fastcgi_buffering).
+
+
+## IIS
+
+When using IIS, you must [disable its buffering](https://support.microsoft.com/en-us/kb/2321250).
+
+## Varnish
+
+When using Varnish, the following VCL disables buffering only for BigPipe responses:
 
 ```
 vcl_fetch {
@@ -49,8 +80,15 @@ vcl_fetch {
 Note that the `big_pipe_nojs` cookie does *not* break caching. Varnish should let that cookie pass through.
 
 
-## Other (reverse) proxies
+## Nginx
+
+When using Nginx, the BigPipe module already sends a `X-Accel-Buffering: no` header for BigPipe responses, which disables buffering.
+
+Alternatively, it is possible to [disable proxy buffering explicitly](http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffering).
+
+
+## Other web servers and (reverse) proxies
 
-Other (reverse) proxies, including CDNs, need to be configured in a similar way.
+Other web servers and (reverse) proxies, including CDNs, need to be configured in a similar way.
 
 Buffering will nullify the improved front-end performance. This means that users accessing the site via a ISP-installed proxy will not benefit. But the site won't break either.