Release download page doesn't work at all with Javascript turned off


The release download page doesn't work at all with Javascript turned off. The courteous thing to do (for those of us surfing with noscript or one of its ilk) is to provide the user a direct download link on the download landing page (you know, the one that says "this download will begin in 3 seconds...").


pranavgk wrote Jul 11, 2013 at 9:24 PM

The JavaScript needs to be turned on, as many important features like download count require JavaScript.

Jaykul wrote Nov 16, 2013 at 6:21 AM

That's just broken. Download counts shouldn't require Javascript -- that would be terrible design.

Jaykul wrote Nov 16, 2013 at 6:24 AM

I'm going to have to push PowerShell module developers to move to other repositories where they can host a download that can be fetched from the console. If CodePlex can't provide a download link that works with Invoke-WebRequest, then there's really just no way to support CodePlex in a PowerShell Package Manager.

martin wrote Nov 16, 2013 at 9:28 AM

So - we're confusing two issues here. The use of Javascript on the download page and the ability for downloads to be performed in a scripted fashion. It sounds like the latter is what you want?

Let me look into this - we deliberately make users see a download page when requesting URL's from the download manager as a measure to prevent abuse of CodePlex hosting (especially by malicious users trying to trick folks into installing stuff on their machine). We do this my making sure you are downloading the file after seeing the download page.

However - there are already some user agents that are excluded from this check so that folks can use them in scripted scenarios and it would make sense to enable this to be done from powershell package managers - forgive my PowerShell naivety, I think Chocolatey when you say that, but are their others I should test with?

Download counts are based off actual downloads from different IP's BTW - not anything to do with the Javascript running in the page. I agree that would be a terrible design ;-)

I should also look at our abuse prevention to see if we're being too cautious in a few other scenarios as well and therefore removing some very useful possibilities.