harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kleymenov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-499) Java 5 Enhancement: java.net.HttpURLConnection should send request head with a connection-field of "Keep-Alive"
Date Thu, 01 Jun 2006 05:37:30 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-499?page=comments#action_12414202 ] 

Alexander Kleymenov commented on HARMONY-499:


I am working on HttpsURLConnection and noticed this JIRA report.

I went through the Java 5 Enhancements for Networking and could not found any statements for

Then I examined the HTTP protocol specification 
(RFC 2616 can be found at http://www.ietf.org/rfc/rfc2616.txt).
It says:
   "HTTP/1.1 applications that do not support persistent connections MUST
   include the "close" connection option in every message."
The source file of HttpURLConnection implementation does not seem to support persistent connections.

So recent changes made to the class


("Connection: close" --> "Connection: Keep-Alive") seem to be incorrect without implementation
of support for persistent connections.


> Java 5 Enhancement: java.net.HttpURLConnection should send request head with a connection-field
of "Keep-Alive"
> ---------------------------------------------------------------------------------------------------------------
>          Key: HARMONY-499
>          URL: http://issues.apache.org/jira/browse/HARMONY-499
>      Project: Harmony
>         Type: Improvement

>   Components: Classlib
>     Reporter: Richard Liang
>     Assignee: Tim Ellison
>     Priority: Minor
>  Attachments: luni.src.net.diff
> Hello,
> java.net.HttpURLConnection should send request head with a default connection-field of
"Keep-Alive". Currently in its implementation, it sends a connection-field of "close", but
does not close its own socket after connection, which may cause low performance and strange
behavior on some servers.
> Best regards,
> Richard

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message