Which RFC describes Proxy-Connection: Keep-Alive ?
Thank you
Markus
On Tue, 5 Apr 2011 22:55:07 +0100, Markus Moeller wrote:
Which RFC describes Proxy-Connection: Keep-Alive ?
Thank you
Markus
AFAICT there is no RFC or even draft. It was a failed experiment from
way, way back.
Current Squid will no longer send it but may (only sometimes) treat it
like
Hi, Amos
For example, we can not browse the following site's flash movie via
squid-3.1.8. squid-3.1.9 could be ok.
http://www.yomiuri.co.jp/stream/
- the famous japanese newspaper site
- please check the only flash movie parts
Probably, the following is the same topic.
[squid-users] Squid
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.
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.
--mkishi
2010/9/9 Henrik Nordström hen...@henriknordstrom.net:
ons 2010-09-08 klockan 14:46 +0900 skrev Mikio Kishi:
It's still a feature, right ?
On the
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
On 08/09/10 17:46, Mikio Kishi wrote:
Hi, Henrik
fre 2007-04-13 klockan 22:25 +0200 skrev Sebastian Weber:
Hendrik, thank you - that solved the problem. Now, I have a new one however:
The client - proxy connection is kept alive correctly. The proxy -
server connection, however, is not.
Hi, Amos
Ah, well. *requiring* things beyond the RFCs (agreed compatible standards)
is a well known cause of failure. Just ask anyone trying to use NTLM on a
public website.
Is multiple POST requests in a http connection using keep-alive RFC
violation ?
--mkishi
On Wed, Sep 8, 2010 at 3:47
On Thu, 9 Sep 2010 01:46:35 +0900, Mikio Kishi mki...@104.net wrote:
Hi, Amos
Ah, well. *requiring* things beyond the RFCs (agreed compatible
standards)
is a well known cause of failure. Just ask anyone trying to use NTLM on
a
public website.
Is multiple POST requests in a http
Hi, Henrik
fre 2007-04-13 klockan 22:25 +0200 skrev Sebastian Weber:
Hendrik, thank you - that solved the problem. Now, I have a new one however:
The client - proxy connection is kept alive correctly. The proxy -
server connection, however, is not. Squid closes the connection to the
server
Hendrik, thank you - that solved the problem. Now, I have a new one however:
The client - proxy connection is kept alive correctly. The proxy -
server connection, however, is not. Squid closes the connection to the
server after the client issues a second request. After that, Squid opens
a new
fre 2007-04-13 klockan 22:25 +0200 skrev Sebastian Weber:
Hendrik, thank you - that solved the problem. Now, I have a new one however:
The client - proxy connection is kept alive correctly. The proxy -
server connection, however, is not. Squid closes the connection to the
server after the
Hi all,
I'm running squid 2.6.STABLE12 and have the following
question:
When a client connects to the proxy and issues a POST
request with HTTP header Proxy-Connection: Keep-Alive,
Squid always answers with Proxy-Connection: close
Is there any way to make Squid accept a Keep-Alive on
POST
tor 2007-04-12 klockan 12:35 +0200 skrev Sebastian Weber:
I'm running squid 2.6.STABLE12 and have the following
question:
When a client connects to the proxy and issues a POST
request with HTTP header Proxy-Connection: Keep-Alive,
Squid always answers with Proxy-Connection: close
Does it?
This is my request:
POST http://127.0.0.1:81/tun/tunnel.php5?a=s HTTP/1.1
Host: 127.0.0.1
Authorization: Basic
Content-Type: application/x-www-form-urlencoded
Proxy-Connection: Keep-Alive
Content-Length: 47
d=%3e3591%0a0%3aeNoLDXYNUkhKTElJ5OUCABfsA2MA%0a
This is what I get in response
tor 2007-04-12 klockan 13:56 +0200 skrev Sebastian Weber:
This is what I get in response from Squid:
HTTP/1.0 200 OK
Content-Type: text/html
X-Cache: MISS from badda
X-Cache-Lookup: MISS from badda:3128
Via: 1.0 badda:3128 (squid/2.6.STABLE12)
Proxy-Connection: close
The response to
16 matches
Mail list logo