has been running using HTTPS for quite a long time now, first on Azure and now on GKE.
avoiding this - possibly for everything under /tzdb, possibly just for latest.txt. But I'd argue that starting off by sending your requests via HTTPS in the first place would be a good plan. I'll make sure that HTTPS keeps working on nodatime.org
- and if you're concerned that I might mess that up (which isn't unreasonable!) you could always consider coding a fallback to HTTP.
Do let me know if you have any thoughts on this. It's actually pretty gratifying to see that we're getting about 2.5qps for tzdb/latest.txt (doubled now due to redirection) - it makes me feel it was worth implementing :)