131402 - text/plain should be exempt from Windows filename extension-adding.

Status: VERIFIED DUPLICATE of bug 120327

(Core Graveyard :: File Handling, defect)

Description

[Jonas Jørgensen]

Build 2002031103, Win2k.

When trying to save <http://www.gerv.net/software/patch-maker/pm>, Mozilla adds
the extension ".txt". This happens because the server sends Content-Type:
text/plain.

I'm filing this under File Handling, but I'm not really sure whether this is
Mozilla's or Gerv's fault. Something needs to be done about this, though, as the
Perl script will not work if it is called anything else than "pm".

Comment 1

[Gervase Markham [:gerv]]

This is a bit of a problem; if I put a file up with no extension, the webserver
sends it as text/plain. This seems reasonable. It also means people can look at
the script online.

Mozilla adds ".txt" on Windows to text/plain files, because it's the local
naming convention. This is also reasonable. 

However, the two together cause problems.

I think I may have to have a "View" link and a "Download" link to a tarball.

Gerv

Comment 2

[Jonas Jørgensen]

That wouldn't solve the problem. I'd still prefer to save the View link since
that would save me the trouble of having to pull the file out of the tarball.

There's also a lot of other sites out there which sends text/plain for files
that aren't really txt files. I don't think it's reasonable to add .txt to
text/plain files. What's the advantage of it anyway? I see why adding .gif to an
image.cgi which sends image/gif can be useful, but I think that text/plain
should be an exception.

Comment 3

[Gervase Markham [:gerv]]

That's a fair point. Reassigning back to default owner for consideration of that
idea.

Gerv

Comment 4

[Boris Zbarsky [:bzbarsky]]

*** This bug has been marked as a duplicate of 120327 ***

Comment 5

[Jonas Jørgensen]

v

Comment 6

[Bill Law]

Perhaps the web server could serve this particular file with an appropriate
Content-Disposition header to specify the save-as name?