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.

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

Re: WebDAV client problem with Authentication

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

To generate 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.
webuser

WebDAV client problem with Authentication

Hi,

The WebDAV client in WinSCP is a must have! I love this function.

Nevertheless, I have some troubles with the authentication with some quite old servers (Novell Webfiles). The problem is that the client is trying to authenticate with the root path of the web server (like "https://www.example.com/"), but these servers can't authenticate to this URL. Instead, they need to use the full path of the user (like "https://www.example.com/oneNet/NetStorage"). I put the full path in the configuration of the site at the entry "Remote Directory", but the logs show that the client is authenticating only to the root path.

Please, can include some modification (a option) to use the full path of the remote directory in the authentication process?

Thank you!

Documentation

Support

Associations

Follow Us