Closed Bug 1182052 Opened 5 years ago Closed 5 years ago

Update download URL for the Public Suffix List copy on publicsuffix.org

Categories

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gerv, Assigned: cliang)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1397] )

+++ This bug was initially created as a clone of Bug #1155581 +++

The IT team maintains hosting for publicsuffix.org, a basic static website served out of SVN.

There are two special URLs for downloads of the Public Suffix List:
https://publicsuffix.org/list/effective_tld_names.dat
https://publicsuffix.org/list/public_suffix_list.dat

This data is not stored in the SVN repo; I belive this is on a CDN for performance reasons. In bug 926891 fubar set up a cron job to pull it every so often and put it wherever it needs to be, and in bug 1155581 the second URL was added.

The request is: can we please now pull from the master copy in Github rather than mozilla-central?

The new URL to pull from is:
https://raw.githubusercontent.com/publicsuffix/list/master/public_suffix_list.dat

Thanks,

Gerv
Summary: Create alias URL for downloading the Public Suffix List → Update download URL for the Public Suffix List copy on publicsuffix.org
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1397]
Assignee: server-ops-webops → cliang
@gerv: I believe that the Public Suffix URLs are now being pulled from the Github copy rather than mozilla-central.  (There are new blogspot-related suffixes.)  Can you please confirm that everything looks correct?


I changed the source URL in the update script, forced the update script to run, and cleared out the older cached copy on the load balancers.
thanks for the heads-up on this, Gervase.  I've updated the debian packaging to use the github upstream as well.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.