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

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

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 7 May 2003 09:28:41 +0200
To: "Roy T. Fielding" <fielding@apache.org>, "Julian Reschke" <julian.reschke@gmx.de>
Cc: <www-tag@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEBBHEAA.julian.reschke@gmx.de>

> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]On Behalf Of
> Roy T. Fielding
> Sent: Wednesday, May 07, 2003 2:16 AM
> To: Julian Reschke
> Cc: www-tag@w3.org
> Subject: Re: Draft TAG finding available: Client handling of MIME
> headers
>
> ....
>
> I didn't say they weren't.  The user can override the interpretation of
> received content.  The owner of a given URI-space can override the
> interpretation of received content.

I see. But unless I miss something, *currently* Apache/moddavs behaviour (to
ignore MIME headers sent by the client) is not only the default, but also
there's really no way to switch that off. This is what I'm concerned with
(not the overall design, but the actual implementation).

> ....
> >
> > Could you please elaborate? In this case, what would be the expected
> > behaviour when I PUT with a content type unknown to the server? Reject
> > it?
>
> That would depend on how you configured the server.  The finding is in
> regards to the interpretation of individual messages and the contents
> of those messages.  If you don't like what the configuration says, then
> change the configuration.

But again that leaves us with possibly misbehaving servers (because they can
be misconfigured), although the clients do indeed supply correct
information. Isn't this contrary to the goals of the draft finding?

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Wednesday, 7 May 2003 03:28:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:32:38 UTC