Work around a bug in Netscape Navigator versions 2.x, 3.x and 4.0b2's

parsing of headers.  If the terminating empty-line CRLF occurs starting
at the 256th or 257th byte of output, then Navigator will think a normal
image is invalid.  We are guessing that this is because their initial
read of a new request uses a 256 byte buffer. We check the bytes written
so far and, if we are about to tickle the bug, we instead insert a
padding header of eminent bogosity.

Submitted by: Roy Fielding and Dean Gaudet, PR#232
Reviewed by: Ken Coar


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/1.3.x@77941 13f79535-47bb-0310-9956-ffa450edef68