On 30/10/10 00:45, Mikio Kishi wrote:
Hi, Henrik
Was the post handling specification modified on squid-3.1.9 ?
On 3.1.9, multi post requests in a http connection became OK.
I think we still misunderstand each other on this thread...
* Multiple POST on a connection has always been allowed.
* Requiring them within a single connection is BAD.
From 3.1.8+ re-use of connections is tried more than earlier releases.
If those broken apps have started working it is more luck than any specs.
--mkishi
2010/9/9 Henrik Nordström<henrik@xxxxxxxxxxxxxxxxxxx>:
ons 2010-09-08 klockan 14:46 +0900 skrev Mikio Kishi:
It's still a feature, right ?
On the Internet, there are some web applications which requires
multi post requests in a http connection...
Applications which require some special relation between connection and
requests are per definition broken.
Connections in HTTP are hop-by-hop, not end-to-end. There is no relation
between connections made by clients to proxy and connections made by the
proxy to requested servers.
You can have N clients connections getting multiplexed over 1 server
connection. Or 1 persistent client connection getting it's requests
distributed over M server connections. Exact result depends on the
traffic and policy of client, proxy and webserver, but the key is that
client<->proxy and proxy<->server connections are fully independent.
An exception to this is if you are using NTLM or Negotiate(kerberos)
authentication, as those authentication protocols is not HTTP
authentication schemes but TCP connection authentication schemes in
direct violation with HTTP messaging rules.
Regards
Henrik
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.8
Beta testers wanted for 3.2.0.2
