I think there are some web server settings
that can effect how jar files are served up. In the past, I seem to recall
some issues on some servers where files with ".php" anywhere
in the file name would routed through some PHP filters, and attempt to
be served up as a php file, hence some jar named something like "org.eclipse.php.jar_versionID"
would end up serving up some HTML error message file that said something
related to "invalid php file". Perhaps its something like
that? And all P2 knows is that the fetch of the jar failed. Just guessing.
Nothing specific about IIS.
p2 is just a bunch of files. Do you have anything setup
to protect from attacks? p2 is looking for a given set of files one by
one (w.o knowing whether or not they exist). I'm thinking that maybe
after a while the IP would be blocked.
On 2010-09-09, at 11:18 AM, Rob Cavallo wrote:
Is there anything particular about a repository as I've been able to successfully
update an exported product when it's being served up by Apache but not
IIS. When using IIS, the update fails prior to completion with an
error "artifact not found" for the product itself after it's