dgaudet     97/04/21 20:01:27

  Modified:    htdocs/manual/misc  FAQ.html
  Log:
  Tweak the wording about the JDK 1.0.2 problem slightly.
  
  Revision  Changes    Path
  1.37      +4 -2      apache/htdocs/manual/misc/FAQ.html
  
  Index: FAQ.html
  ===================================================================
  RCS file: /export/home/cvs/apache/htdocs/manual/misc/FAQ.html,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -C3 -r1.36 -r1.37
  *** FAQ.html  1997/04/22 02:55:43     1.36
  --- FAQ.html  1997/04/22 03:01:25     1.37
  ***************
  *** 8,14 ****
    <!--#include virtual="header.html" -->
    <H1>Apache Server Frequently Asked Questions</H1>
    <P>
  ! $Revision: 1.36 $ ($Date: 1997/04/22 02:55:43 $)
    </P>
    <P>
    If you are reading a text-only version of this FAQ, you may find numbers
  --- 8,14 ----
    <!--#include virtual="header.html" -->
    <H1>Apache Server Frequently Asked Questions</H1>
    <P>
  ! $Revision: 1.37 $ ($Date: 1997/04/22 03:01:25 $)
    </P>
    <P>
    If you are reading a text-only version of this FAQ, you may find numbers
  ***************
  *** 864,870 ****
      processing a request.  Unfortunately, the Java Development Kit (JDK)
      version 1.0.2 URL methods (URLConnection and friends) expect to see
      the version string &quot;HTTP/1.0&quot; and do not correctly interpret
  !   the &quot;HTTP/1.1&quot; 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.
      </P>
  --- 864,872 ----
      processing a request.  Unfortunately, the Java Development Kit (JDK)
      version 1.0.2 URL methods (URLConnection and friends) expect to see
      the version string &quot;HTTP/1.0&quot; and do not correctly interpret
  !   the &quot;HTTP/1.1&quot; value Apache is sending (this part of the
  !   response is a declaration of what the server can do rather than a
  !   declaration of the dialect of the response).  The result is that
      the JDK methods do not correctly parse the headers, and include them
      with the document content by mistake.
      </P>
  
  
  

Reply via email to