Re: Failure of Java HTTP, some puzzles for those with not enough to do

Here is a list of URLs that a browser can read but that Java's HTTP
get/head cannot.

http://ask.com/
http://cgi.omroep.nl/cgi-bin/streams?/rnw/smac/2004/amsterdam_forum__chomsky_on_iraq_and_war_on_terror_20051216_low.rm
http://www.akademika.no/
http://www.amnesty.org/en/library/asset/AMR51/145/2004/en/b6ab0f58-d570-11dd-bb24-1fb85fe8fa05/amr511452004en.html
http://www.bechtel.com/
http://www.downloadplex.com/Submit-Software.html
http://www.glish.com/css/7.asp
http://www.microsoft.com/windows/windowsmedia/download/AllDownloads.aspx
http://www.os2site.com/sw/internet/time/clock2.htm
http://www.qantas.com.au/travel/airlines/home/au/en
http://www.telegraph.co.uk/news/yourview/1562772/David-Cameron-answers-your-questions.html
http://www.thefreedictionary.com/
https://player.helixcommunity.org/2008/help/playerfaq.html
https://tsa.aloaha.com/
https://wush.net/svn/mindprod
https://www.eecs.harvard.edu/mailman/listinfo/jopt-users

Harvard is because they use their own SSL cert
aloaha is a timestamp service

Sometimes it is because they give some sort of failed response code
but deliver the page anyway.

Sometimes I sort out what screwy thing they are doing (e.g. circular
redirects) and write, but they almost never correct the problem.

In the days of the telephone, if you attached some device that was not
behaving according to spec the telephone company would demand you
disconnect it, and when you did they would reconnect service. There
seems to be no equivalent in the Internet world.