Dne Wed, 17 Oct 2007 00:34:49 +0200 Kazantsev Alexey <[EMAIL PROTECTED]>
napsal/-a:
> RFC 2068:
>
> 19.7.1 Compatibility with HTTP/1.0 Persistent Connections
>
> Some clients and servers may wish to be compatible with some previous
> implementations of persistent connections in HTTP/1.0 clients and
> servers. Persistent connections in HTTP/1.0 must be explicitly
> negotiated as they are not the default behavior. HTTP/1.0
RFC 2616:
19.6.2 Compatibility with HTTP/1.0 Persistent Connections
The problem was that some existing 1.0 clients may be
sending Keep-Alive to a proxy server that doesn't understand
Connection, which would then erroneously forward it to the next
inbound server, which would establish the Keep-Alive connection and
result in a hung HTTP/1.0 proxy waiting for the close on the
response. The result is that HTTP/1.0 clients must be prevented from
using Keep-Alive when talking to proxies.
> If client explicit use "Connection: keep-alive" header and server
> understad it, why not?
If you want it, then you could try following:
1. to set property Keep-alive=TRUE to prevent Synapse from
inserting "Connection: close" into header
2. to supply header "Connection: Keep-alive" explicitly
3. to set protocol to 1.1
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
