Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Username

Subject

Message body

Font colour:

Font size:

Options

Disable BBCode in this post

Notify me when a reply is posted (registered users only)

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

Filename

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

File Comment

Options

Private file (available to author and site moderators only)

Topic review

krolch

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

2018-01-15 11:22

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

martin

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

2018-01-12

Thanks for the log.

The server violates WebDAV RFC 4918 by sending:

<D:timeout>300</D:timeout>

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.

krolch

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

2018-01-08 13:55

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

martin

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

2017-12-28

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

krolch

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

2017-12-21 14:23

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

martin

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

2017-12-21

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

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.

Krolch

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

2017-12-20 13:05

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.