FYI, wget is banned from central. So, you should not even try it to "diagnose" conn problems :)
~t~ On Fri, Nov 28, 2008 at 4:08 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Hi Robert, > > Artifactory doesn't use a unique user-agent, which further compounded > the trouble finding this problem. I can't confirm which versions of > Artifactory have this issue and even if we could, they all appear to be > using the exact same user-agent so there's not much we could do to > separate it out. > > > > --Brian > > > > From: Robert Oschwald [mailto:[EMAIL PROTECTED] > Sent: Friday, November 28, 2008 9:42 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; Maven Users List; Maven Project > Management Committee List > Subject: Re: [Artifactory-users] Artifactory 1.3 has been DOS'ing > theCentral repository > > > > Brian, > > > > thanks for the info. > > We recognized several problems accessing the repo using Artifactory last > week. We are on Version 1.2.5u1, which is not affected, right? > > We figured out that the connection problems were only seen on some http > clients, like wget, but not with others like ff,ie,lynx. > > > > So my question is: Have you blocked access for all artifactory versions > last week or was it just due to the performance problems? If you blocked > access to all artifactory versions (I think on the agent field), could > you distinguish between "good" and "bad" versions? > > > > Robert > > > > To protect the Maven Community from ongoing troubles, we have > had to take the extra-ordinary step of blocking all downloads of the > index file by Artifactory until this is resolved. Upon doing this, the > traffic has fallen to 10% of what it has been in the recent past. If you > are using Artifactory, please adjust this cron definition to run only > weekly and save yourself and us tons of wasted bandwidth and money. > > -- Thanks, ~t~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
