You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/12/09 06:41:58 UTC
[jira] Commented: (MRM-1429) Proxying of xml files from one archiva
server to another fails, when jar files succeed
[ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246962#action_246962 ]
Brett Porter commented on MRM-1429:
-----------------------------------
I was able to reproduce on the steps you've used
> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
> Key: MRM-1429
> URL: http://jira.codehaus.org/browse/MRM-1429
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.3.1
> Environment: ubuntu 10.10 32bit x86
> Reporter: Dave Brosius
> Priority: Minor
> Fix For: 1.3.3
>
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
> Identifier: proxy
> Name: Proxy of Local
> URL: http://localhost:8080/archiva/repository/internal/
> UserName: as defined
> Password: as defined
> Timeout in Seconds: 60
> Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
> Network Proxy: (direct connection)
> Managed Repository: internal
> Remote Repository: proxy
> (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
> Group Id: com.mebigfatguy
> Artifact Id: fb-contrib
> Version: 4.6.0
> Packaging: jar
> Classifier: (blank)
> Generate Maven 2 POM: checked
> Artifact file: fb-contrib.jar
> Repository Id: internal
> and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
> http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
> and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
> Group Id: com.mebigfatguy
> Artifact Id: build
> Version: 4.6.0
> Packaging: xml
> Classifier: (blank)
> Generate Maven 2 POM: checked
> Artifact file: build.xml
> Repository Id: internal
> and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
> http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
> and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
> http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
> Artifact is *not downloaded *and get this error page
> HTTP ERROR 404
> Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
> Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira