In the east coast server (the source server) i see failed attempts to find the jar on it's list of external maven repositories, so i know that the request is making it to that server.
To be clear, the client just hangs waiting for the request to complete. The xml files were added to archiva thru the archiva web interface. Perhaps this was a misstep by me: When i added them, the 'packaging' attribute i gave was xml, that's correct right? Again, these files are correctly pulled when clients go directly against the east coast server. It's only when there is a proxy involved that there are problems. ----- Original Message ----- From: "Wendy Smoak" <[email protected]> Sent: Wed, October 27, 2010 14:37 Subject:Re: Proxy problems with non .jar files On Wed, Oct 27, 2010 at 2:22 PM, David Brosius <[email protected]> wrote: > For instance .xml files in the east coast repository are not proxied into > the west coast server, and thus don't make it to the west coast client > developers. Does anything interesting show up in the logs (on either side) when you make a request for the file? Are the xml files proper artifacts with checksums and metadata? How did they get into Archiva? -- Wendy ----- End of original message -----
