top-level .htaccess file missing in the ftp tree

RESOLVED FIXED

Status

--
major
RESOLVED FIXED
11 years ago
4 years ago

People

(Reporter: nthomas, Assigned: justdave)

Tracking

Details

(Reporter)

Description

11 years ago
A nightly tester noticed that Minefield tries to display .dmg files downloaded from the new ftp.m.o., rather than offer to save them. (Incidentally, Minefield copes less gracefully than Fx2 does, see bugs 396726, 396732).

Could we make sure all the custom types in surf/manna's apache config are copied over to the new box ?

Comment 1

11 years ago
Added:

AddType application/octet-stream .dmg 

To apache.  
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
Can't find this in the vhost file, I'll move it there (as well as checking for anything else on manna that didn't make it).  These need to go in the vhost file for the affected domain, not in the main httpd.conf, otherwise it'll get lost again next time we move to a new machine (like it did this time).
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: server-ops → justdave
Status: REOPENED → NEW
Is the list of content-type changes up-to-date on http://www.mozilla.org/mirroring.html? If not, please update it, along with all the size data and other things on that page.
Summary: dm-ftp1 - add Content-Type for .dmg (and other files we commonly serve) → dm-ftp01 - add Content-Type for .dmg (and other files we commonly serve)
This turns out to be fallout from the big rsync to the netapp last night.  The top-level .htaccess file never made it to the new tree.  This means we lost the filetype overrides on all the releases mirrors as well.
Summary: dm-ftp01 - add Content-Type for .dmg (and other files we commonly serve) → top-level .htaccess file missing in the ftp tree
OK, the .htaccess file has been copied over, and the mirroring.html page has been updated to reflect reality (may need to wait for the cache to expire to see the new version).
Status: NEW → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.