W3C home > Mailing lists > Public > www-tag@w3.org > May 2003

Re: Draft TAG finding available: Client handling of MIME headers

From: Roy T. Fielding <fielding@apache.org>
Date: Tue, 6 May 2003 13:08:14 -0700
Cc: <www-tag@w3.org>
To: "Julian Reschke" <julian.reschke@gmx.de>
Message-Id: <7849339F-7FFE-11D7-8C85-000393753936@apache.org>

> Let's assume that an HTTP user agent uses PUT to send an entitity body 
> to an
> HTTP server, but neglects to provide a content-type header. What's the
> recommend server behaviour for subsequent GET requests to that 
> resource?
> 1) do not send a content type header (server refuses to guess),
> 2a) guess content type based on "extension" (hmph...) or
> 2b) guess content type based on content (for instance after 
> successfully
> parsing as HTML)
> 3) ...?
> Note that 2a) is what currently Apache/moddav does, and this really 
> seems to
> be a very bad idea.

It is what the owner of that URI-space has configured the server to do.
The reason it does that is to support a whole host of features beyond
webdav that should not be disabled just because one authoring interface
has no knowledge of them.

Received on Tuesday, 6 May 2003 16:07:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:58 UTC