Change Details

The https://dumps.wikimedia.org/ service is a web interface for downloading various data sets produced by the Wikimedia community. This service has been around for many years. I assume that this longevity is why this service is still using it's own public IPv4 address and local TLS termination to serve files to the world.

The https://dumps.wikimedia.org/ service is a web interface for downloading various data sets produced by the Wikimedia community. This service has been around for many years. I assume that this longevity is why this service is still using it's own public IPv4 address and local TLS termination to serve files to the world. todo: * [x] Add new dumps-rsync service name * [ ] {T415193} * [ ] Make nginx trust XFF from our caches * [ ] Add internal DNS name to be used for DNS backend * [ ] Add CDN backend mapping (to cache-upload?) * [ ] Check for any bandwidth limits * [ ] Migrate DNS to point to cache-upload * [ ] Firewall off direct access once TTLs have expired * [ ] Migrate to internal cfssl certs?

The https://dumps.wikimedia.org/ service is a web interface for downloading various data sets produced by the Wikimedia community. This service has been around for many years. I assume that this longevity is why this service is still using it's own public IPv4 address and local TLS termination to serve files to the world. todo: * [x] Add new dumps-rsync service name * [ ] {T415193} * [ ] Make nginx trust XFF from our caches * [ ] Add internal DNS name to be used for DNS backend * [ ] Add CDN backend mapping (to cache-upload?) * [ ] Check for any bandwidth limits * [ ] Migrate DNS to point to cache-upload * [ ] Firewall off direct access once TTLs have expired * [ ] Migrate to internal cfssl certs?