[ZCM] [ZC] 879/ 2 Comment "incorrect DAV:getcontenttype for collections"

[Collector: Zope Bugs, Features, and Patches ...]

Issue #879 Update (Comment) "incorrect DAV:getcontenttype for collections"
 Status Pending, Zope/bug medium
To followup, visit:
  http://zope.org/Collectors/Zope/879

==============================================================
= Comment - Entry #2 by regebro on Oct 28, 2003 5:49 am

The root page has no content-type in Zope, since it has no content. When you do a GET on it, since it has no content, it will instead be rendered, and the rendition will be sent as the GET result. The rendition has a content-type of text/html. 

Possible solutions to this is to let contenttype default to text/html instead of defaulting to an empty string as it does today. I don't know what side effects this may have.

________________________________________
= Request - Entry #1 by Anonymous User on Apr 10, 2003 12:28 pm

When I do a GET on the root page of www.zope.org, the returned Content-Type is text/html. However, when I do a PROPFIND, the returned DAV:getcontenttype property is the empty string.
The WebDAV spec states that the property should match the Content-Type header for a GET. The two are different, which is broken.

This problem was originally discovered as part of a perceived bug against Subversion. That bug has additional discussion which may be interesting:
http://subversion.tigris.org/issues/show_bug.cgi?id=1238

==============================================================