incorrect DAV:getcontenttype for collections

Bug #142536 reported by Bug Importer on 2003-04-10
Affects Status Importance Assigned to Milestone
Zope 2
Won't Fix

Bug Description

When I do a GET on the root page of, 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:

Lennart Regebro (regebro-gmail) wrote :

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.

Tres Seaver (tseaver) wrote :

This pseudo-requirement is impossible to satisfy: the content type of the GET request for the container
can be set dynamically by the view method / template for the container, which we are not going to consult
for the PROPFIND request.

Changed in zope2:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers