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.

Options
Add an Attachment

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

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

Options

Topic review

martin

Thanks. Well, the server returns 200 OK with content-type: text/xml in response to DELETE request. And returns no data.

That's not a valid response for two reasons:

  • With 200 response, the body should not be empty (as opposite to 204 No content)
  • XML cannot be empty.

So WinSCP (or rather neon) behaves correctly (while it might be more tolerant). But the problem is imo on the server side. It should not return content-type: text/xml and it should return 204.
dsanke

here is the log.
martin

Re: fake error message when deleting file on webdav server

Thanks for your report.
Can you post a session log file both from 6.2.3 and the latest version?

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.
dsanke

Could it be a problem caused by neon version bump?
dsanke

Fake error message when deleting file on WebDAV server

Could not parse response: XML parse error at line 1: no element found

WinSCP 6.2.4 RC and above give me this error when I deleting file on WebDAV server (Mixplorer on an Android phone). WinSCP 6.2.3 RC and below do not have this issue.
The file was deleted with or without this error message.