Re: Content type

Hi,

On Mon, Mar 15, 2004 at 02:13:05PM -0600, [email protected] 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