The background: I'm trying to do a batch upload to a server (which backends into Apache's Jakarta Project's "slide" WebDAV implementation) providing DAV but *not plain HTTP* methods to its clients. Cadaver works; Microsoft's WebDAV implementation works; lftp doesn't. This is most unfortunate, as lftp is the only one of these which is reasonably scriptable.
cadaver, when logging on, starts out with an OPTIONS requests and graduates to PROPFIND. Both of these succeed. lftp, when logging on, makes a HEAD request which fails with a 401 (even when the username and password are undeniably correct -- I should probably have a chat w/ the developer about choosing a better error to respond with). It makes no further attempts to communicate with the server after this point. Is this by-design, or is it behaviour which may be fixed in some future version? Personally, I'd rather like to see webdav:// as a replacement for http://, to indicate that DAV methods should be used.
