Closed Bug 1517138 Opened 6 years ago Closed 6 years ago

I can't download firefox (404 error)

Categories

(www.mozilla.org :: Pages & Content, defect)

Product:
www.mozilla.org
Component:
Pages & Content
Version:
Production
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: phil_falco, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 Steps to reproduce: 1. Go to this page: https://www.mozilla.org/en-US/firefox/new/?f=139 2. Click 'Download Now' I'm on windows 10 (tried with chrome and edge with no luck). Actual results: 404 Expected results: I should've downloaded firefox
Severity: normal → major
Component: Untriaged → Miscellaneous
Product: Firefox → mozilla.org
Summary: I CAN'T DOWNLOAD FIREFOX BECAUSE OF A 404 → I can't download firefox (404 error)
Version: unspecified → other
Severity: major → minor
Found a work around by going to mozilla.org, not sure why google taking me to https://www.mozilla.org/en-US/firefox/new/?f=139
(In reply to phil_falco from comment #1) > Found a work around by going to mozilla.org, not sure why google taking me > to https://www.mozilla.org/en-US/firefox/new/?f=139 Here's the google search used to get to that link: https://www.google.com/search?q=firefox&oq=firefox&aqs=chrome.0.69i59l2j69i60l3j0.1587j0j7&sourceid=chrome&ie=UTF-8
Component: Miscellaneous → Pages & Content
Product: mozilla.org → www.mozilla.org
Version: other → Production
Looks like this is a regression from bug 1493595.
Blocks: 1493595
This issue is caused by a funnelcake experiment. I have disabled the experiment effective immediately via the commit above. I'll try and uncover what went wrong here. Many thanks for the report!

Alex - any update as to the root cause here?

Flags: needinfo?(agibson)

This issue was resolved some time ago.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(agibson)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.