Remove support for the Binary Content extension [RFC3516].

“If the server does not know how to decode the section's CTE, it MUST
fail the request and issue a "NO" response that contains the
"UNKNOWN-CTE" extended response code.” — [RFC3516 section 4.3]

Unfortunately the client doesn't know which message couldn't be decoded,
so it can't fallback and use BODY instead.

This made ‘use-binary=NO’ pretty much mandatory.  Hence we remove
support for BINARY [RFC3516].  Instead, we increase the thresold for
when to add Zlib full flush points from 4096 to the buffer size (32768).

1 files changed, 0 insertions, 4 deletions

diff --git a/Changelog b/Changelog
index 9d864f8..67f6833 100644
--- a/Changelog
+++ b/Changelog
@@ -6,10 +6,6 @@ interimap (0.2) upstream;
     server.
   * Add a configuration option 'null-stderr=YES' to send STDERR to
     /dev/null for type=tunnel.
-  * Add support for the Binary Content extension [RFC3516].  Enabled by
-    default if both the local and remote servers advertize "BINARY".
-	Can be disabled by adding 'use-binary=NO' to the default section in
-	the configuration file.
   * Exit with return value 0 when receiving a SIGTERM.
   * Add SSL options SINGLE_ECDH_USE, SINGLE_DH_USE, NO_SSLv2, NO_SSLv3
     and NO_COMPRESSION to the compiled-in CTX options.