"Unknown Error" when changing into webdav-directory with active lock

Hi there!

I'm trying to list a directory on a remote server via webdav. When doing that for a directory that contains a file with an active lock, I get an "Unknown Error" an no directory contents are displayed.

Using the debug-level in WinSCP and analyzing the log, it seems that there are problems parsing the "timeout" tag in the server's response:

---
. 2017-12-20 12:14:42.199 XML: end-element (268, {DAV:, lockscope})
. 2017-12-20 12:14:42.199 XML: start-element (267, {DAV:, timeout}) => 272
. 2017-12-20 12:14:42.199 XML: char-data (272) returns 0
. 2017-12-20 12:14:42.199 XML: end-element for 272 failed with -1.
. 2017-12-20 12:14:42.199 XML: end-element (272, {DAV:, timeout})
. 2017-12-20 12:14:42.199 sess: Closing connection.
. 2017-12-20 12:14:42.200 sess: Connection closed.
. 2017-12-20 12:14:42.200 Request ends, status 207 class 2xx, error line:
. 2017-12-20 12:14:42.200 207 Multi-Status
. 2017-12-20 12:14:42.200 Running destroy hooks.
. 2017-12-20 12:14:42.200 Request ends.
* 2017-12-20 12:14:42.208 (ECommand) Fehler beim Anzeigen des Verzeichnisses "[REMOVED BY AUTHOR]".
* 2017-12-20 12:14:42.208 Unknown error
---

I sniffed the server's response and to me it looks like valid XML around the timeout-Tag. Here's a snippet:

---
<D:lockscope><D:exclusive/></D:lockscope><D:timeout>300</D:timeout><D:depth>0</D:depth>
---

Is this a WinSCP-XML-Parsing issue? I'm running the latest Version (5.11.3)

Any help kindly appreciated.

Please attach a full session log file showing the problem (using the latest version of WinSCP).

martin wrote:

Please attach a full session log file showing the problem (using the latest version of WinSCP).

Hi Martin,

thanks very much for your quick reply. Ich added the requested logfile (private)to this post. The problem when parsing the timeout-tag can be found in line 1983.

Thanks alot!

Krolch

Thanks. Can you post a log on level Debug 2?

martin wrote:

Thanks. Can you post a log on level Debug 2?

Hi Martin,

here weg go - logfile with level Debug 2 attached.

Cheers,

Krolch

Thanks for the log.

The server violates WebDAV RFC 4918 by sending:
While the RFC in sections 14.29 and 10.7 define that the <timeout> tag should have format Seconds-300 (or Infinite).
https://datatracker.ietf.org/doc/html/rfc4918#section-14.29

Consider contacting a server vendor to request fixing the bug.

Hi Martin,

thanks very much for your reply and your profound analysis of the problem.
I just contacted the vendor to get the server-side patched.

Kind regards

krolch