A workaround is needed for servers which provide no correct resource type.

Bug #1083022 reported by Tobias Schlauch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python WebDAV Library
Fix Released
High
Tobias Schlauch

Bug Description

Here an example server which causes the problem: http://dav.mentor.ieee.org:80/

If the property is not available, check the leading "/" (available -> collection, not available resource).

Related branches

summary: - A workaround is needed for servers which provide no correct rsource
+ A workaround is needed for servers which provide no correct resource
type.
Changed in python-webdav-lib:
milestone: none → 0.4.0
Revision history for this message
Tobias Schlauch (tobias-schlauch) wrote :

A closer look at the problem showed:
- In general, the server correctly uses the resourcetype property.
- Only the root collection causes the problem: The property has not been correctly selected from the property response!

Changed in python-webdav-lib:
importance: Undecided → High
assignee: nobody → Tobias Schlauch (tobias-schlauch)
status: New → Fix Committed
Changed in python-webdav-lib:
status: Fix Committed → Fix Released
Revision history for this message
Tobias Schlauch (tobias-schlauch) wrote :

The source of the problem is that the depth header for PROP* requests is not correctly interpreted. depth=0 and depth=1 return the same: requested source and the children.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.