From f60be7455acec658f742888ee3dd8f1873f1ac4a Mon Sep 17 00:00:00 2001 From: Evgeny Kotkov Date: Mon, 10 Apr 2017 16:02:04 +0000 Subject: [PATCH] mod_brotli: Nuke the section about input decompression using mod_brotli in the documentation. Currently, mod_brotli only allows dynamic output compression, and doesn't have the server-side decompression capability. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1790869 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_brotli.xml | 29 ----------------------------- 1 file changed, 29 deletions(-) diff --git a/docs/manual/mod/mod_brotli.xml b/docs/manual/mod/mod_brotli.xml index 36c597c27f..5995cff33d 100644 --- a/docs/manual/mod/mod_brotli.xml +++ b/docs/manual/mod/mod_brotli.xml @@ -96,35 +96,6 @@ SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-brotli -
Input Decompression -

The mod_brotli module also provides a filter for - decompressing a brotli compressed request body . In order to activate - this feature you have to insert the BROTLI_COMPRESS filter into - the input filter chain using SetInputFilter or AddInputFilter, for example:

- - -<Location "/dav-area"> - SetInputFilter BROTLI_COMPRESS -</Location> - - -

Now if a request contains a Content-Encoding: - brotli header, the body will be automatically decompressed. - Few browsers have the ability to brotli request bodies. However, - some special applications actually do support request - compression, for instance some WebDAV clients.

- - Note on Content-Length -

If you evaluate the request body yourself, don't trust - the Content-Length header! - The Content-Length header reflects the length of the - incoming data from the client and not the byte count of - the decompressed data stream.

-
-
Dealing with proxy servers -- 2.50.1