malformed WebDAV response

Bug #143441 reported by Dirk Datzert
2
Affects Status Importance Assigned to Milestone
Zope 2
Invalid
Medium
Unassigned

Bug Description

Hi,

we have detected a WebDAV issue between SAP-Portal and ZOPE as a KM-WebDAV-Repository.

If the SAP-Portal create a new folder named 'New_Folder' in a Zope directory, some properties come along with the creating request which should be ignored or maybe better rejected by Zope since it is not supported by Zope.

If you will access this New_Folder after creating Zope will respond with an invalid XML-response, I have attached the malformed response.

Regards,
Dirk

Tags: bug zope
Revision history for this message
Dirk Datzert (dirk.datzert) wrote :
Revision history for this message
Florent Guillaume (efge) wrote :

Could you also provide the original creation request sent by SAP to Zope ? Maybe by doing a network trace. What properties are unsupported by Zope ?

Revision history for this message
Dirk Datzert (dirk.datzert) wrote :

Uploaded: dav1.txt

Hi,

I have recorded the complete process of creating a new folder called "New%20Folder" under directory /test3 on my server into 3 log-files dav1.txt - dav3.txt

I think that the error is only in dav3.txt

Regards,
Dirk

Revision history for this message
Dirk Datzert (dirk.datzert) wrote :

Uploaded: dav2.txt

Revision history for this message
Dirk Datzert (dirk.datzert) wrote :

Uploaded: dav3.txt

Revision history for this message
Dirk Datzert (dirk.datzert) wrote :

I would say that the correct propstat of the last response in dav3.txt should be:

<d:propstat
  xmlns:n="http://sapportals.com/xmlns/cm/collaboration"
  xmlns:pf="http://sapportals.com/xmlns/cm/webdav">
  <d:prop>
  <n:SingleDiscTreeNodeProperty pf:hidden="false">0</n:SingleDiscTreeNodeProperty>
  </d:prop>
  <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>

Best Regards,
Dirk

Revision history for this message
Hanno Schlichting (hannosch) wrote :

Little has changed in webdav over the years, so this is likely still true.

Changed in zope2:
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

The zope2 project on Launchpad has been archived at the request of the Zope developers (see https://answers.launchpad.net/launchpad/+question/683589 and https://answers.launchpad.net/launchpad/+question/685285). If this bug is still relevant, please refile it at https://github.com/zopefoundation/zope2.

Changed in zope2:
status: Confirmed → Invalid
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.