Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Reply-To: <rbb@covalent.net>
From: "Ryan Bloom" <rbb@covalent.net>
To: <dev@httpd.apache.org>
Subject: RE: Protocol question: 304 and content-length
Date: Sun, 14 Apr 2002 12:46:39 -0700
Organization: Covalent Technologies
Message-ID: <001e01c1e3ed$18a8e240$0a01230a@KOJ>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3CB9DC25.352DE142@sharp.fm>
Importance: Normal


According to the spec, IIS is incorrect, and we have done the correct
thing.

Ryan

> Someone posted a bug report in bugzilla claiming that they were having
> problems with an IIS v4.0 server returning blank pages through an
Apache
> proxy. They posted a trace of the request, and this is what the IIS
> server said in response to a conditional request (If-None-Match):
> 
> HTTP/1.1
> 304 Not Modified
> Server: Microsoft-IIS/4.0
> Date: Thu, 04 Apr 2002 16:05:15 GMT
> Content-Location: http://www.dreo.dnd.ca/index.html
> ETag: "c077721eaf49c01:1364"
> Content-Length: 0
> 
> The above response includes a content-length of zero. RFC2616 10.3.5
> says that the cache MUST update the entry with the field values in the
> response.
> 
> ie: The content-length just forced the cached file to be of zero
length.
> 
> Looks like a bug in IIS to me - can anyone else confirm this?
> 
> Regards,
> Graham
> --
> -----------------------------------------
> minfrin@sharp.fm		"There's a moon
> 					over Bourbon Street
> 						tonight..."