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

>> No, what I said is that assuming webdav is the sole source of such
>> information is wrong.  The server config files are just as 
>> authoritative
>> as an individual PUT request.  If the server config says that a filter
>
> Are they? What's the architectural reason to say that MIME header sent 
> by
> servers are authorative, while those sent by clients aren't?

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.

>> is applied or metadata assigned based on the storage file name, then
>> that is exactly what the server will do.
>>
>>> 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.  Whether or not mod_dav will do
>
> 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.

....Roy

Received on Tuesday, 6 May 2003 20:29:01 UTC