1198036 - releases.mozilla.org, ftp.mozilla.org, archive.mozilla.org throws a 403 Forbidden

Status: RESOLVED FIXED

(Infrastructure & Operations :: MOC: Problems, task)

Description

[Ashish Vijayaram [:ashish]]

> 15:26:20 < nagios-phx1> Mon 15:26:20 PDT [1115] releases.mozilla.org:HTTP is WARNING: HTTP WARNING: HTTP/1.1 403 Forbidden - 4267 bytes in 0.319 second response time (http://m.mozilla.org/HTTP)

Can confirm with curl:

$ curl -L -I http://releases.mozilla.org
HTTP/1.1 301 Moved Permanently
Server: Apache
X-Backend-Server: pp-web01
Vary: Accept-Encoding
Content-Type: text/html; charset=iso-8859-1
Date: Mon, 24 Aug 2015 22:27:13 GMT
Location: http://download.cdn.mozilla.net/
Transfer-Encoding: chunked
Connection: Keep-Alive
X-Cache-Info: cached

HTTP/1.1 403 Forbidden
Server: Apache
X-Backend-Server: ftp8.dmz.scl3.mozilla.com
Content-Type: text/html; charset=UTF-8
Accept-Ranges: bytes
Access-Control-Allow-Origin: *
X-Cache-Info: caching
Content-Length: 3985
Date: Mon, 24 Aug 2015 22:27:25 GMT
Connection: keep-alive

Comment 1

[Ashish Vijayaram [:ashish]]

http://ftp.mozilla.org/ and http://archive.mozilla.org/ show the default apache config page

Comment 2

[Ashish Vijayaram [:ashish]]

This has been fixed. Suspect root cause - an automated and routine httpd upgrade caused a default configuration file to be put back in place.

Comment 3

[Jake Maul [:jakem]]

Puppet upgraded Apache, and the new package restored the default "welcome.conf" file, which had previously been deleted from the FTP cluster. This config file detects when an index file is not present, and instead shows the welcome page.

It's intended to show some sort of helpful info for when you first set up a new web server and there is no site to show yet. it just so happens that ftp.mozilla.org (and related names) aren't a real website and are just a directory of files to download... exactly what welcome.conf tries to avoid. :)

I've deleted the file (and restarted Apache), so we're back to normal. I've also set puppet to make sure this file is absent on the FTP cluster, so in the future this should theoretically not happen again.


For the record: files subdirectories worked throughout. http://ftp.mozilla.org/pub/ and similar were displayed normally, and any direct links to files or directories were not affected. This only affected people (and Nagios-like tools) that were checking the root. This is because welcome.conf only looks at the root.