W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: Content Sniffing impact on HTTPbis - #155

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 14 Jun 2009 11:52:54 +0200
Message-ID: <4A34C876.5080403@gmx.de>
To: Werner Baumann <werner.baumann@onlinehome.de>
CC: Adrien de Croy <adrien@qbik.com>, Adam Barth <w3c@adambarth.com>, Jamie Lokier <jamie@shareable.org>, ietf-http-wg@w3.org
Werner Baumann wrote:
> Am Sun, 14 Jun 2009 08:46:02 +0200
> schrieb Julian Reschke <julian.reschke@gmx.de>:
> 
>> Many HTTP servers that are also WebDAV servers will store the mime
>> type as separate meta data, and will also allow clients to specify it
>> when doing a PUT.
>>
> Do you know servers that really get this right?

At least one (SAP KM), but I'm quite sure this is also true for others, 
such as Apache Jackrabbit or Xythos WFS.

> I am asking because I once tried to implement setting MIME-type in
> davfs2 (using PROPPATCH). I did my first tests with
> Apache/mod_dav/mod_dav_fs and IIS and then immediately stopped work on
> this. What I got is:
> PROPFIND returned the MIME-type as set by davfs2
> GET and HEAD returned another MIME-type, the one derived from the file
> extension.

Well, that's a bug. No matter what it returns, it should be consistent. 
It may be a good idea to open a bug wrt to Apache/mod_dav then.

BR, Julian
Received on Sunday, 14 June 2009 09:53:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:03 GMT