(expanding on theory #2: from a quick sampling, it looks like the failures here are in new-tab code. And we do have one new-tab-associated file with a hardcoded usage of this server URL: https://searchfox.org/mozilla-central/rev/560bbebd595cf2f6a9861f3f67dd0739f4c4c559/browser/components/newtab/data/content/activity-stream.bundle.js#1506 https://searchfox.org/mozilla-central/rev/560bbebd595cf2f6a9861f3f67dd0739f4c4c559/browser/components/newtab/content-src/components/ASRouterAdmin/ASRouterAdmin.jsx#1119 Presumably that code *should* the pref-controlled server value preferentially, but it's not clear to me whether (or where) it does that right now.
Bug 1714615 Comment 78 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(expanding on theory #2: from a quick sampling, it looks like the failures here are in new-tab code. And we do have two new-tab-associated files with a hardcoded usage of this server URL: https://searchfox.org/mozilla-central/rev/560bbebd595cf2f6a9861f3f67dd0739f4c4c559/browser/components/newtab/data/content/activity-stream.bundle.js#1506 https://searchfox.org/mozilla-central/rev/560bbebd595cf2f6a9861f3f67dd0739f4c4c559/browser/components/newtab/content-src/components/ASRouterAdmin/ASRouterAdmin.jsx#1119 Presumably that code *should* the pref-controlled server value preferentially, but it's not clear to me whether (or where) it does that right now.