Django Issue Tracker inaccessible due to expired certificate (code.djangoproject.com) 2 points by Humphrey 4y ago ↗ HN
[–] Humphrey 4y ago ↗ Certificate expired 2022-02-03 which, depending on your timezone, means that you can't access it.Since they have enabled HSTS, browsers will not let you add an exception, so this site is effectively offline for my half of the world. [–] CaliforniaKarl 4y ago ↗ > …which, depending on your timezone, means that you can't access it.Certificate expirations are encoded in the certificate as UTC, so everyone would see the expiration at around the same time.(That of course assumes a certain amount of client clock accuracy, the same cert being served to everyone across the world, etc.…) [–] [deleted] 4y ago ↗ (comment deleted)
[–] CaliforniaKarl 4y ago ↗ > …which, depending on your timezone, means that you can't access it.Certificate expirations are encoded in the certificate as UTC, so everyone would see the expiration at around the same time.(That of course assumes a certain amount of client clock accuracy, the same cert being served to everyone across the world, etc.…)
[–] CaliforniaKarl 4y ago ↗ The site is working for me. Per crt.sh, it looks like a new cert was issued not too long ago (https://crt.sh/?id=6097757307); it must now be in production.
4 comments
[ 2.7 ms ] story [ 20.3 ms ] threadSince they have enabled HSTS, browsers will not let you add an exception, so this site is effectively offline for my half of the world.
Certificate expirations are encoded in the certificate as UTC, so everyone would see the expiration at around the same time.
(That of course assumes a certain amount of client clock accuracy, the same cert being served to everyone across the world, etc.…)