diff options
author | Ken Coar <coar@apache.org> | 1997-05-06 15:12:35 +0000 |
---|---|---|
committer | Ken Coar <coar@apache.org> | 1997-05-06 15:12:35 +0000 |
commit | ad1aef1091d4f7fafc26e572f57ee775cddfcaed (patch) | |
tree | 254e6cf8f0c1fa296e0091a0eec2149e64a68188 | |
parent | 0748b1431fe2608564ecfd89dcbb49d341f6d392 (diff) | |
download | httpd-ad1aef1091d4f7fafc26e572f57ee775cddfcaed.tar.gz |
Added semi-FAQ about Java JDX 1.? and Apache's HTTP/1.1 headers.
I suspect this one's going to come up a *lot* once 1.2 is
formally released and a substantial number of those 400,000
servers out there upgrade..
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@78116 13f79535-47bb-0310-9956-ffa450edef68
-rw-r--r-- | docs/manual/misc/FAQ.html | 29 |
1 files changed, 28 insertions, 1 deletions
diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 57169fd061..270bc99727 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -8,7 +8,7 @@ <!--#include virtual="header.html" --> <H1>Apache Server Frequently Asked Questions</H1> <P> - $Revision: 1.55 $ ($Date: 1997/05/05 01:30:04 $) + $Revision: 1.56 $ ($Date: 1997/05/06 15:12:35 $) </P> <P> The latest version of this FAQ is always available from the main @@ -170,6 +170,9 @@ <LI><A HREF="#addlog">How do I add browsers and referrers to my logs?</A> </LI> + <LI><A HREF="#jdk1.x">Why do Java applets and applications not work + with documents on my Apache server?</A> + </LI> </OL> </LI> </UL> @@ -1338,6 +1341,30 @@ Logfiles</CITE></A>". </P> <HR> + </LI> + <LI><A NAME="jdk1.x"> + <STRONG>Why do Java applets and applications not work + with documents on my Apache server?</A></STRONG> + </A> + <P> + The Java Development Kit (JDK) libraries versions 1.0.2 and 1.1 do not + correctly interpret the "<SAMP>HTTP/1.1</SAMP>" response + header that Apache 1.2 sends. Instead, if they don't see an exact + match for "<SAMP>HTTP/1.0</SAMP>", they assume the headers + are part of the document content. + </P> + <P> + This is a known problem, and it has been reported to Sun's JavaSoft + unit. In the meantime, Apache 1.2 servers can work around this by + adding the following lines to their configuration files: + </P> + <DL> + <DD><CODE>BrowserMatch HotJava/1. force-response-1.0 + <BR> + BrowserMatch Java1. force-response-1.0</CODE> + </DD> + </DL> + <HR> <!-- Don't forget to add HR tags at the end of each list item.. --> </LI> </OL> |