Just ran some tests and for me it seems that the server/application configuration checks for signs of download spiders/robots to lock them out. Unfortunately many people are using download managers that add an information to the "User-Agent" header to indicate their presence (in my case FreeDownloadManager that adds "FDM").
Trying to the page using IE returns a HTTP 302 redirect to /forbidden.html. Using the same headers but with the FDM removed everything works well.
Original Request sent by IE:Code: Select all
GET /sf/frs/do/viewRelease/projects.joomla/frs.joomla_1_0.1_0_6 HTTP/1.1
Accept: */*
Referer: http://www.joomla.org
Accept-Language: de,en;q=0.5
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; FDM; .NET CLR 2.0.50727)
Host: developer.joomla.org
Connection: Keep-Alive
By sending the same request without "; FDM" I was able to get the right result.
So, what is causing this ? I would say that either the security related setup of the Forge application or the container configuration should be checked ;o)
I hope this helps a little bit to finally correct this behaviour since the current settings will lock 5 percent or even more of potential users (according to my statistics abour 50% are using IE.
Kindest regards
Falk