In message <4e2466028alists-nospam(a)vigay.com>
Paul Vigay <lists-nospam(a)vigay.com> wrote:
In article <cf4d64244e.tim(a)south-frm.demon.co.uk>,
Tim Powys-Lybbe <tim(a)powys.org> wrote:
[Snip]
> I would recommend that you, Peter, try to avoid arguments against the man
> (the (a) type) and stick to arguments against the words (the (b) type).
As it so happens, Peter was wrong on both counts.
I'm afraid not.
My 'assumption' was that NetSurf was corrupting binary downloads, which
Peter confirmed by his last sentence.
No, I didn't. I said it was uncompressing them. It's not corrupting
them.
Therefore it was perfectly reasonable. It /was/ corrupting binary
downloads in that it was changing them from the original source
without notifying me. Thus, as far as my server was concerned, they
/were/ corrupted files.
No. The interpretation of corruption was on your part. The files were
intact. And your server (and by that, you really mean one specific
program) would certainly have understood them if you had, for example,
renamed them. Not what you expect is not the same as corrupt.
No browser should automatically try to process file downloads, at
least without warning the user first and giving the option to not
'gunzip' them.
Close, but once again, not entirely correct. In some circumstances
gunzipping really is the most appropriate and useful thing to do. I
agree that it wasn't ok in this case. Moreover, it isn't the browser
doing the gunzipping - it's the server, on the browser's request.
And so, given these further assertions that you haven't checked, as well
as recent outbursts on your part elsewhere with things you could have
just put a bit more effort into getting correct (e.g, the ridiculous
banner on
riscos.org), you'll certainly understand if I stand by both my
original comments.
--
Peter Naulls - peter(a)chocky.org |
http://www.chocky.org/
----------------------------------------------------------------------------
RISC OS Community Wiki - add your own content |
http://www.riscos.info/