maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Zhuo (JIRA)" <>
Subject [jira] Commented: (MRM-419) WebDAV functionality not working for Internet Explorer / Windows Network Places
Date Fri, 10 Aug 2007 17:38:13 GMT


Dan Zhuo commented on MRM-419:

I have installed archiva 1.0-alpha-2 standalone on both windows and linux, it appears the
same problem. More precisely, it would work properly if clicking the WebDav links from admin
repositories management pages. However, It is not work properly if typing the WebDav links
directly into web browsers (both IE 6, 7 and Firefox 2.0.6). i.e. click any links for
would collapse the "REPOSITORY-ID".   

> WebDAV functionality not working for Internet Explorer / Windows Network Places
> -------------------------------------------------------------------------------
>                 Key: MRM-419
>                 URL:
>             Project: Archiva
>          Issue Type: Bug
>          Components: WebDAV interface
>    Affects Versions: 1.0-alpha-2
>            Reporter: John Didion
>            Assignee: Joakim Erdfelt
>             Fix For: 1.0.x
> I am using archiva built from source (r548493). I set up a managed repository and several
proxied repositories. 
> Browsing the WebDAV url from Firefox works just fine, but it appears the IE doesn't recognize
the url - it asks me if I want to "save this file", and its type is unknown. 
> When I try to set up a Network Place using the url, it shows me the top level of the
repository, but if I try to browse to any folder, I get the error: "Documents in this folder
are not available. The folder may have been moved or deleted, or network problems may be preventing
a connection to the server. There is a problem with the web server. Please try again later
or contact the server administrator." 
> I notice that the url it's trying to browse to is incorrect. The root URL of the repository
> http://[host]/archiva/repository/internal/
> but when I double-click on, say, commons-collections, it tries to browse to:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message