From: dgaudet Date: Sun, 21 Dec 1997 08:18:13 +0000 (+0000) Subject: Tweak the 257th byte bug... happens at the 256th byte as well. X-Git-Tag: APACHE_1_3b5~37 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f03de05016a072c19411f154960df3930fdef75a;p=thirdparty%2Fapache%2Fhttpd.git Tweak the 257th byte bug... happens at the 256th byte as well. Reviewed by: Jim Jagielski, Brian Behlendorf git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@79754 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html index 7da780013a3..2910924bad5 100644 --- a/docs/manual/misc/known_client_problems.html +++ b/docs/manual/misc/known_client_problems.html @@ -129,11 +129,11 @@ This workaround is available in 1.2.2, and in a

All versions of Navigator from 2.0 through 4.0b2 (and possibly later) have a problem if the trailing CRLF of the response header starts at -the 256th or 257th byte of the response. A BrowserMatch for this would +offset 256, 257 or 258 of the response. A BrowserMatch for this would match on nearly every hit, so the workaround is enabled automatically on all responses. The workaround is to detect when this condition would occur in a response and add extra padding to the header to push the -trailing CRLF past the 257th byte of the response. +trailing CRLF past offset 258 of the response.

Multipart responses and Quoted Boundary Strings