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 01:38:33 +0200
To: <www-tag@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEPPHDAA.julian.reschke@gmx.de>

> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org]On Behalf Of
> Martin Duerst
> Sent: Tuesday, May 06, 2003 11:24 PM
> To: Roy T. Fielding; Julian Reschke
> Cc: www-tag@w3.org
> Subject: Re: Draft TAG finding available: Client handling of MIME
> headers
> ...
> >>If a client PUTs a UTF-8 encoded XML document and properly declares both
> >>type and encoding, but a subsequent GET returns different (and wrong!)
> >>information this really smells like a bug, not a feature.
> >
> >What the server should do is reject the PUT if the metadata is
> >inconsistent with its configuration.
> Why shouldn't the server just update the configuration?
> Is there anything in the HTTP spec that says that server
> configuration is more important than the metadata attached
> to a document?

Thanks, Martin :-)

Aren't we just reviewing a draft TAG finding that says that MIME headers are

So I really don't see how Apache/moddav's current behaviour can be
considered correct -- it's not like the server administrator currently can
make a conscious decision to respect MIME headers sent by the client. The
default handling is to ignore them, and there's no way to change that
(unless I oversee a config option -- if I do I'd really love to learn about
that one).


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 6 May 2003 19:38:44 UTC

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