News for hackers. Stuff that matters.
Re:The long and sordid history of the user-agent HTTP header... by cubicle on Sunday July 15, 2012 @04:55PM (#4248084)
?

  bbot@magnesium:~> wget http://en.wikipedia.org/wiki/Japanese_yen
  --2012-07-15 13:54:29--  http://en.wikipedia.org/wiki/Japanese_yen
  Resolving en.wikipedia.org... 208.80.154.225, 2620:0:861:ed1a::1
  Connecting to en.wikipedia.org|208.80.154.225|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 203481 (199K) [text/html]
Re:The long and sordid history of the user-agent HTTP header... by verroq on Monday July 16, 2012 @02:56AM (#4249643)
wget uses the "wget/version" useragent.
Re:The long and sordid history of the user-agent HTTP header... by cubicle on Monday July 16, 2012 @04:22PM (#4252410)
Yes, I am aware. The point of my comment is that Wikipedia obviously does not block wget.
Re:The long and sordid history of the user-agent HTTP header... by verroq on Monday July 16, 2012 @08:46PM (#4253530)
The point is that if it becomes a problem they'll just block that particular useragent.
Re:The long and sordid history of the user-agent HTTP header... by cubicle on Tuesday July 17, 2012 @12:44AM (#4254127)
The point is that you can use -U to specify arbitrary user-agent strings, and -E robots=off to ignore robots.txt.

User-agent blocking is completely braindead. It does nothing at all. The fact that somebody in 2012 can possibly think it works is astounding to me.