www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martijn de Vries <mart...@shop.com>
Subject general/6430: Java 1.3.0 UrlConnection does not handle HTTP/1.1 content-encoding.
Date Fri, 18 Aug 2000 15:19:20 GMT

>Number:         6430
>Category:       general
>Synopsis:       Java 1.3.0 UrlConnection does not handle HTTP/1.1 content-encoding.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Fri Aug 18 08:20:01 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     martijn@shop.com
>Release:        1.3.12
>Organization:
apache
>Environment:
Linux colossus 2.2.13 #4 SMP Tue Nov 30 15:00:16 EST 1999 i686 unknown

>Description:

The Java 1.3.0 UrlConnection class does not handle HTTP/1.1 correctly. We are
seeing numbers show up in the content that are correctly removed by browsers 
such as IE5.

It would be nice for the default httpd.conf file to contain something like this:
BrowserMatch "Java/1\.3\.0" downgrade-1.0

--------------------------------------------------------------------------------
A seperate issue:

After reading the documentation it seemed to me that 'force-response-1.0' should
be able to do the trick as well, however Apache still gives HTTP/1.1 responses 
(sometimes using content-encoding) when a User-Agent header matches a 
'BrowserMatch "Blah" force-response-1.0' statement.

Example (this particular reply does not happen to use the content-encoding 
I mentioned before but it does show that a HTTP/1.1 reply is given eventhough
the 'User-Agent: JDK/1.0' header should have triggered the BrowserMatch 
statement to give a HTTP/1.0 reply).
GET / HTTP/1.1
Host: blah.com:5080
User-Agent: JDK/1.0

HTTP/1.1 200 OK
Date: Fri, 18 Aug 2000 14:57:33 GMT
Server: Apache/1.3.12 (Unix) ApacheJServ/1.1.2 mod_ssl/2.6.5 OpenSSL/0.9.5a
Last-Modified: Wed, 09 Aug 2000 18:48:06 GMT
ETag: "1420ce-28-3991a766"
Accept-Ranges: bytes
Content-Length: 40
Content-Type: text/html

<HTML>
Blah
</HTML>

-------------------------------------------------------------------------------

In any case, once Apache has been forced to give HTTP/1.0 replies to Java 1.3.0 
browsers, everything works fine. I have not tested this for Java 1.2.

>How-To-Repeat:
see above
>Fix:
see above
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 


Mime
View raw message