Search squid archive

persistent HTTP broken in 202 Accepted

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: squid-users@xxxxxxxxxxxxxxx
Subject: persistent HTTP broken in 202 Accepted
From: Miguel A Paraz <mparaz@xxxxxxxxx>
Date: Thu, 15 Sep 2005 09:05:51 +0800
Delivered-to: mailing list squid-users@xxxxxxxxxxxxxxx
Mailing-list: contact squid-users-help@xxxxxxxxxxxxxxx; run by ezmlm
Reply-to: mparaz@xxxxxxxxx

Hi,
I noticed that in Squid 2.5.9, if the server responds with a HTTP/1.0
202 Accepted, squid breaks the persistent connection with Connection:
close. If I go direct to the server - it's the Nokia MMSC and not a
standard HTTP server - 202 does not break the connection. Is this
proper HTTP spec behavior?

Follow-Ups:
- Re: persistent HTTP broken in 202 Accepted
  - From: Henrik Nordstrom

Prev by Date: RE: Question on acl files
Next by Date: Re: Restricting certain users to certain urls
Previous by thread: WCCP and iptables
Next by thread: Re: persistent HTTP broken in 202 Accepted
Index(es):
- Date
- Thread

[Index of Archives] [Linux Audio Users] [Samba] [Big List of Linux Books] [Linux USB] [Yosemite News]

Powered by Linux