Community
Participate
Working Groups
Zope (www.zope.org) contains an integrated WebDAV server. The Eclipse WebDAV plugin doesn't send authorization data to such a Zope-WebDAV-Server, instead it presents a dialog with an exception "Error communicating with DAV server: 401 Unauthorized". Username and password are correct, and other WebDAV tools like cadaver establish an authenticated connection to the server. A tcpdump trace reveals that Eclipse usually sends a HTTP PROPFIND request without "Authorization:" line first. If the server responds with HTTP code 401 (unauthorized), it sends the same request again, this time with an authorization field. This behaviour can be observed with Apache2 DAV, for example. With a Zope DAV server, however, the second request is never sent, instead the exception is shown to the user. My guess: Apache DAV sends back an "HTTP/1.1 401 Authorization required", while Zope DAV sends "HTTP/1.1 401 Unauthorized" - perhaps there is a bug in the status code parser?
I concur. I am seeing exactly the same thing (eclipse 3.1.1), and the analysis of the problem is exactly what I supposed was happening too.
Same goes for cocoon applications, where 401: Unauthorinzed is the default behaviour.
This component is no longer being actively developed. We encourage users to investigate the capabilities of the Eclipse Web Tools Project.