Closed Bug 528747 Opened 15 years ago Closed 15 years ago

What is update.mozilla.org, and why does it have a self signed cert?

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: faaborg, Assigned: fox2mike)

References

Details

Yesterday my friend said the following to me: "I googled for the "read it later" extension, and clicked on the mozilla link, but it just resulted in an error page." The first hit in the google search results was to update.mozilla.org, and it was using a self signed cert. However following the process today, it doesn't seem to be listed anymore in the google search results, so perhaps the problem is already addressed.
update.mozilla.org was the URL for the add-ons site before it was addons.mozilla.org. We did clean up all of the old URLs to redirect to AMO instead of serving AMO from that domain a few months ago, so these URLs will only redirect to AMO now. I did a Google search for update.mozilla.org and did see at least one add-on with an old URL like https://update.mozilla.org/extensions/moreinfo.php?id=77 so maybe we should give update.mozilla.org its own robots.txt that doesn't redirect to AMO's robots.txt to disallow everything?
Assignee: nobody → server-ops
Component: Public Pages → Server Operations
Product: addons.mozilla.org → mozilla.org
QA Contact: web-ui → mrz
Version: unspecified → other
How about doing a 301 to amo?
Assignee: server-ops → shyam
Can we kill DNS for this?
(In reply to comment #2) > How about doing a 301 to amo? That works for me if we aren't already doing it. Not sure about killing DNS -- if we really want to do that it will take some more thought to make sure we aren't missing anything. Old versions of Firefox still ping UMO for add-on updates.
Redirect is now in place.
Status: NEW → RESOLVED
Closed: 15 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.