[tor-commits] [torspec/master] Prop #278: Be explicit about handling both ".z"-suffixes and "plaintext" files.

[ahf at torproject.org]

commit c512794f54894b75f3fea0b07a2d5ffc81f3be96
Author: Alexander Færøy <ahf at torproject.org>
Date:   Fri Apr 7 13:19:23 2017 +0200

    Prop #278: Be explicit about handling both ".z"-suffixes and "plaintext" files.
---
 proposals/278-directory-compression-scheme-negotiation.txt | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/proposals/278-directory-compression-scheme-negotiation.txt b/proposals/278-directory-compression-scheme-negotiation.txt
index b1f2808..b62c69a 100644
--- a/proposals/278-directory-compression-scheme-negotiation.txt
+++ b/proposals/278-directory-compression-scheme-negotiation.txt
@@ -88,12 +88,14 @@ Target: N/A
     Accept-Encoding: x-zstd, x-lzma2, gzip, deflate
 
   When a directory server receives a request with the "Accept-Encoding"
-  header included it must decide on a mutually supported compression
-  scheme and add the "Content-Encoding" header to its response and thus
-  notifying the client of its decision. The "Content-Encoding" header
-  can at most contain one supported compression scheme. If no mutual
-  compression scheme can be negotiated the server must respond with an
-  HTTP error status code of 415 "Unsupported Media Type".
+  header included, to either the ".z" compressed or the uncompressed
+  version of any given document, it must decide on a mutually supported
+  compression scheme and add the "Content-Encoding" header to its
+  response and thus notifying the client of its decision. The
+  "Content-Encoding" header can at most contain one supported
+  compression scheme. If no mutual compression scheme can be negotiated
+  the server must respond with an HTTP error status code of 415
+  "Unsupported Media Type".
 
   For example: