From 9f0b3774454aec3352c9da5fba6a33df3a04f2e9 Mon Sep 17 00:00:00 2001 From: Ken Coar Date: Mon, 21 Apr 1997 13:43:28 +0000 Subject: [PATCH] Added a bunch of to-do items from questions received by ApacheWeek, and added a Q&A about the Java JDK 1.0.2 problem with HTTP/1.1 headers. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@77946 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/FAQ.html | 52 +++++++++++++++++++++++++++++++++++++-- 1 file changed, 50 insertions(+), 2 deletions(-) diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 9fb1d29d35..2cbd0da143 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -8,7 +8,7 @@

Apache Server Frequently Asked Questions

-$Revision: 1.27 $ ($Date: 1997/04/20 15:40:06 $) +$Revision: 1.28 $ ($Date: 1997/04/21 13:43:28 $)

If you are reading a text-only version of this FAQ, you may find numbers @@ -30,6 +30,20 @@ do not appear, and are not needed, for the hypertext version. + + + + + + + + + + + + + +

@@ -814,7 +831,8 @@ do not appear, and are not needed, for the hypertext version.
  • Why don't my cookies work, I even compiled in mod_cookies? - + +

    Firstly, you do not need to compile in mod_cookies in order for your scripts to work (see the previous question @@ -823,6 +841,36 @@ do not appear, and are not needed, for the hypertext version. be because your script does not work properly or your browser does not use cookies or is not set-up to accept them.

    +
    +
    • +
  • + Why do my Java app[let]s give me plain text when I request + an URL from an Apache server? + +

    + As of version 1.2, Apache is an HTTP/1.1 (HyperText Transfer Protocol + version 1.1) server. This fact is reflected in the protocol version + that's included in the response headers sent to a client when + processing a request. Unfortunately, the Java Development Kit (JDK) + version 1.0.2 URL methods (URLConnection and friends) expect to see + the version string "HTTP/1.0" and do not correctly interpret + the "HTTP/1.1" value Apache is sending. The result is that + the JDK methods do not correctly parse the headers, and include them + with the document content by mistake. +

    +

    + This is definitely a bug in the JDK, but it's unclear when (or + whether) it will be fixed. In the meantime, a workaround is to tell + Apache to "fake" an HTTP/1.0 response to requests that come + from the JDK methods; this can be done by including a line such as the + following in your server configuration files: +

    +

    +

    +
    BrowserMatch HotJava/1.0 force-response-1.0 +
    +
    +

    • -- 2.40.0