From: brian Date: Wed, 20 May 1998 01:22:52 +0000 (+0000) Subject: PR: 2066 X-Git-Tag: APACHE_1_3b7~9 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f27852e6fafd61675b339ccec9b12211718d9dc8;p=thirdparty%2Fapache%2Fhttpd.git PR: 2066 Submitted by: Ronald Tschalaer Added note about JDK 1.2 betas having HTTP problems. Thanks Ronald. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@81308 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/known_client_problems.html b/docs/manual/misc/known_client_problems.html index 7bfafaa7ad4..729d88abe72 100644 --- a/docs/manual/misc/known_client_problems.html +++ b/docs/manual/misc/known_client_problems.html @@ -216,6 +216,26 @@ There's also some information about the actual problem. +

JDK 1.2 betas lose parts of responses.

+ +

The http client in the JDK1.2beta2 and beta3 will throw away the first part of +the response body when both the headers and the first part of the body are sent +in the same network packet AND keep-alive's are being used. If either condition +is not met then it works fine. + +

See also Bug-ID's 4124329 and 4125538 at the java developer connection. + +

If you are seeing this bug yourself, you can add the following BrowserMatch +directive to work around it: + +

+BrowserMatch "Java1\.2beta[23]" nokeepalive +
+ +

We don't advocate this though since bending over backwards for beta software +is usually not a good idea; ideally it gets fixed, new betas or a final release +comes out, and no one uses the broken old software anymore. In theory. +