1619243 - Source code checkout README should be served as text/plain

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Tristan Miller]

The various SeaMonkey release pages (e.g., https://www.seamonkey-project.org/releases/2.53.1) link to a README.txt (e.g., https://archive.mozilla.org/pub/seamonkey/releases/2.53.1/README.txt) with instructions on how to fetch the source code. This README.txt is always served with the MIME type binary/octet-stream -- see below for sample output from wget. Serving the file this way means that web browsers (including SeaMonkey itself) generally refuse to display the file, instead forcing the users to download it. This is rather annoying; it would be nice if the file were instead served with the MIME type text/plain.

$ wget -S https://archive.mozilla.org/pub/seamonkey/releases/2.53.1/README.txt
--2020-03-02 13:16:31-- https://archive.mozilla.org/pub/seamonkey/releases/2.53.1/README.txt
Resolving archive.mozilla.org (archive.mozilla.org)... 99.86.243.6, 99.86.243.105, 99.86.243.88, ...
Connecting to archive.mozilla.org (archive.mozilla.org)|99.86.243.6|:443... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Content-Type: binary/octet-stream
Content-Length: 1538
Connection: keep-alive
Date: Mon, 02 Mar 2020 12:16:33 GMT
Last-Modified: Fri, 28 Feb 2020 00:25:46 GMT
ETag: "92cea1fc938c2d2ea28724f51743f1bc"
x-amz-version-id: GBwUjVdgCA5pv1vpbvfXun21RnRI27km
Accept-Ranges: bytes
Server: AmazonS3
X-Cache: Miss from cloudfront
Via: 1.1 650962b00c259fe47c193b15b2fe4b88.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: VIE50-C1
X-Amz-Cf-Id: Iw2gZmei7JgEUhVvdXlJqw-wCEXPGxp6D_Fb0UGpGhMVgjsy-Mv0Qw==
Length: 1538 (1.5K) [binary/octet-stream]

Comment 1

[Ian Neal]

I suspect this is something that Mozilla currently control on ftp.mozilla.org
ewong?

Comment 2

[Edmund Wong (:ewong)]

(In reply to Ian Neal from comment #1)

I suspect this is something that Mozilla currently control on ftp.mozilla.org
ewong?

I'll take a gander at the file. I know for a fact that I upload as text, UNLESS, somehow a bom
crept into the README.txt file generation.

Comment 3

[Edmund Wong (:ewong)]

I've checked the readme file and it isn't a binary file nor does it have a bom.

That said, I've tried "curl -D h.txt --output readme.txt https://archive.mozilla.org/pub/seamonkey/releases/2.53.1/README.TXT"
and also see that it's a binary octet-stream.

Comment 4

[Edmund Wong (:ewong)]

Should be fixed as bug 1620809 is fixed.