On Tue, Aug 25, 2009 at 10:07 PM, Aaron Griffin<aaronmgriffin@xxxxxxxxx> wrote: > On Tue, Aug 25, 2009 at 9:38 PM, David C. > Rankin<drankinatty@xxxxxxxxxxxxxxxxxx> wrote: >> On Tuesday 25 August 2009 07:25:27 pm Pierre Schmitz wrote: >>> Am Mittwoch 26 August 2009 01:49:52 schrieb David C. Rankin: >>> > I'm glad to finally know what the problem is, but it may not be >>> > helpful to Arch to have the repos killed by some configured (or >>> > misconfigured) web traffic analyzer package... >>> >>> pacman does not load any html web pages anyway; so there is no problem at >>> all. >>> >> >> Pierre, >> >> I know you are right, but how do you get around the http:// protocol? I look >> at the mirrorlist and I see: >> >> # United States >> Server = http://mirror.rit.edu/archlinux/$repo/os/i686 >> Server = http://archlinux.unixheads.org/$repo/os/i686 >> ^^^^^^^^^^^^^^^^^^^^^^^^^ >> <snip remaining US repos> >> >> How does pacman get around it? Wouldn't it be subject to whatever is >> monitoring http requests on that site just like any other page or file? >> >> Hopefully, the hang is just a temporary issue there, but probably every 3rd >> or 4th update pacman has been hanging. It hasn't done that in the 3-4 months >> I've enjoyed arch, just in the past few days. Hopefully the atavism will >> subside. > > Google Analytics is javascript. pacman does not parse, understand, or > even care about javascript. Nor does it ever even hit the URL you are referring to. It goes after files only, not directories (which are probably index listings). -Dan
