Re:Incident report: Some GOV.UK URLs blocked by deceptive si...
by mananaysiempre on Tuesday November 29, 2022 @04:47AM
(#33785549)
> Shouldn't gov.uk just stick to domains under .gov.uk?
TFA says this was the intention, and the govuk.digital address never worked outside the internal network (the subdomain in question does resolve right now, but that seems to be it).
Given that *.production.govuk.digital is presumably accompanied by *.staging.govuk.digital or similar, I can see why they took out a separate domain for internal purposes, e.g. so that breaking DNS for it does not immediately put the whole of public-facing gov.uk on fire, or so that the CDN can pick up backend IP changes without modifications to the gov.uk DNS zone, or for some other infrastructural reason. It’s not like domains are expensive, and this one honestly looks like it might have been left from the time they were rolling out the whole thing.
(TIL you can set favicon URLs for non-HTML documents: apparently putting rel="shortcut icon" in the HTTP Link header should work? Although gov.uk is not doing that right now.)
TFA says this was the intention, and the govuk.digital address never worked outside the internal network (the subdomain in question does resolve right now, but that seems to be it).
Given that *.production.govuk.digital is presumably accompanied by *.staging.govuk.digital or similar, I can see why they took out a separate domain for internal purposes, e.g. so that breaking DNS for it does not immediately put the whole of public-facing gov.uk on fire, or so that the CDN can pick up backend IP changes without modifications to the gov.uk DNS zone, or for some other infrastructural reason. It’s not like domains are expensive, and this one honestly looks like it might have been left from the time they were rolling out the whole thing.
(TIL you can set favicon URLs for non-HTML documents: apparently putting rel="shortcut icon" in the HTTP Link header should work? Although gov.uk is not doing that right now.)