Thanks, Mark! I noticed this defect in Mozilla earlier when writing my web interface but didn't have the time to investigate fully.

Quote:
Does anyone know if Mozilla responds well to bug reports?

The reason I said it might not be a bug is because the Content-Disposition header that is used to suggest the filename to the browser is not a standard header in HTTP 1.0 or 1.1 - it is from the MIME standard, and browser writers can even ignore it completely if they like. Certainly Mozilla should have kept parsing to the end of the line, and IE should recognize double quotes, but both of them are supporting a de facto standard in their own way, like so so many other little quirks. Sucks donuts.