[prev in list] [next in list] [prev in thread] [next in thread]
List: publicfile
Subject: Re: Content type
From: Peter Conrad <conrad () tivano ! de>
Date: 2004-03-16 8:19:01
Message-ID: 20040316081901.GB1164 () tivano ! de
[Download RAW message or body]
Hi,
On Mon, Mar 15, 2004 at 02:13:05PM -0600, mw-list-publicfile@csi.hu wrote:
>
> It turns out, that yum sends an HTTP/1.1 request. Is it true then
> that the following from rfc2616 (section 4.4 Message length) applies:
>
> 3.If a Content-Length header field (section 14.13) is present,
> its decimal value in OCTETs represents both the entity-length
> and the transfer-length. The Content-Length header field MUST
> NOT be sent if these two lengths are different (i.e., if a
> Transfer-Encoding header field is present). If a message is
> received with both a Transfer-Encoding header field and a
> Content-Length header field, the latter MUST be ignored.
> In other words, publicfile is correct when in the following
> conversation does not send Content-Length:
Yes. And note that even if content-length was present in the response,
according to the excerpt above the client would have to ignore it.
Bye,
Peter
--
Peter Conrad Tel: +49 6102 / 80 99 072
[ t]ivano Software GmbH Fax: +49 6102 / 80 99 071
Bahnhofstr. 18 http://www.tivano.de/
63263 Neu-Isenburg
Germany
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic