A browser's default behaviour should be treating it as an executable, because people that know/care they are zip files (the minority) will know how to override that behaviour, whilst people that don't will get all confused.
Well, if there's different content types to specify that, then yeah.
(And, if it hasn't explicitly been set by the uploader, the default behaviour should again be to determine if its an executable JAR and act accordingly.)
my browser (IE8) did detect it and act accordingly - maybe spinningplates has buggered about with some settings or installed some software that hijacked the .jar extension?
I can't be bothered figured out what you're saying there; I'm hungry and have stuff to do.
The JAR provided was an executable one. Unless someone explicitly said "don't treat this as an executable" (which wasn't done because there's no functionality to do that on Beehive's attachment page) then it should have been detected as an executable and passed down the chain to the browser which should have said "this is an executable jar, run or save?"
And what it definitely shouldn't have done is tacked on a .zip extension, because it already has a valid extension, (and because it isn't a pure zip).
And now I'm going to go eat and not let myself get distracted so I can get stuff finished. :@
