You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org> on 2004/10/29 10:19:39 UTC
[jira] Commented: (AXISCPP-176) Make axis2 transport work with Keep-Alive
[ http://issues.apache.org/jira/browse/AXISCPP-176?page=comments#action_54794 ]
Samisa Abeysinghe commented on AXISCPP-176:
-------------------------------------------
>From http://www.io.com/~maus/HttpKeepAlive.html:
HTTP/1.0
Under HTTP 1.0, there is no official specification for how keepalive operates. It was, in essence, tacked on to an existing protocol. If the browser supports keep-alive, it adds an additional header to the request:
Connection: Keep-Alive
Then, when the server receives this request and generates a response, it also adds a header to the response:
Connection: Keep-Alive
Following this, the connection is NOT dropped, but is instead kept open. When the client sends another request, it uses the same connection. This will continue until either the client or the server decides that the conversation is over, and one of them drops the connection.
HTTP/1.1:
Under HTTP 1.1, the official keepalive method is different. All connections are kept alive, unless stated otherwise with the following header:
Connection: close
The Connection: Keep-Alive header no longer has any meaning because of this.
Additionally, an optional Keep-Alive: header is described, but is so underspecified as to be meaningless. Avoid it.
> Make axis2 transport work with Keep-Alive
> -----------------------------------------
>
> Key: AXISCPP-176
> URL: http://issues.apache.org/jira/browse/AXISCPP-176
> Project: Axis-C++
> Type: Improvement
> Components: Transport (Client)
> Versions: future (enh)
> Environment: All platforms
> Reporter: Samisa Abeysinghe
> Assignee: Samisa Abeysinghe
> Priority: Minor
> Fix For: 1.4 Alpha
>
> Make the client transport to process incomming headers and deal with "Connection: Keep-Alive" HTTP header.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira