W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1998

RE: is DAV:getcontenttype read only?

From: Alex Hopmann (Exchange) <alexhop@exchange.microsoft.com>
Date: Fri, 18 Dec 1998 20:22:30 -0800
Message-ID: <E46F2E74BFC4CF119A8B00805FCCAB2705CC31FA@RENCHOW>
To: "'John Stracke'" <francis@netscape.com>, w3c-dist-auth@w3.org
I believe in our implementation, the property is writable. The server will
save the Content-type included with a PUT, but a client can also change that
value later (via PROPPATCH) without having to retransmit the whole resource.

Alex

-----Original Message-----
From: John Stracke [mailto:francis@netscape.com]
Sent: Friday, December 18, 1998 2:26 PM
To: w3c-dist-auth@w3.org
Subject: Re: is DAV:getcontenttype read only?


Jim Davis wrote (some time ago--I'm still catching up from email that came
in
while I was on sabbatical):

> The spec (13.5) does not say whether the DAV:getcontenttype property is
> readonly or not.  In mod_dav it is, in PyDAV it is not.
>
> I claim it should not be read-only, as the client (who stored the resource
> via PUT) has better knowledge of the server (which can, at best, be
relying
> on resource name heuristics to guess the content type).

Shouldn't the server save the value of the Content-Type: that came in on the
PUT?

--
/======================================================================\
|John (Francis) Stracke    |My opinions are my own.| S/MIME supported  |
|Software Retrophrenologist|===========================================|
|Netscape Comm. Corp.      |Almost no one has ever wanted a 1/4" drill |
|francis@netscape.com      | bit; all they ever wanted was a 1/4" hole.|
\======================================================================/
Received on Friday, 18 December 1998 23:24:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:48 GMT