Overview of binaries.openttd.org and related domains

binaries-overview.txt

(some parts allow HTTP, instead of redirecting HTTP to HTTPS, because the OpenTTD client cannot use HTTPS)

HTTP+HTTPS binaries.openttd via ALB
	/bananas	-> forwarded ECS openttd/content-server
	/installer	-> redirect 301 installer.cdn.openttd.org

HTTPS binaries.openttd via ALB
	/bananas	-> 404 (files changed to md5-name)
	/binaries	-> redirect 301 cdn.openttd.org
	/extra		-> redirect 301 cdn.openttd.org
	/releases	-> redirect 301 cdn.openttd.org
	/nightlies	-> 404 (URLs changed anyway, and people are only trying to download old (subversion) nightlies)
	/custom		-> 404 (no longer available)

HTTP+HTTPS installer.cdn.openttd.org via CloudFront
	S3 bucket
	Populated by GitHub repository "installer", with some GitHub actions automation
	In there a YAML file which says which OpenTTD clients should get which Open[GMS]FX version
	Makes sure the .7z files are created if they don't exist yet

HTTP+HTTPS bananas.cdn.openttd.org via CloudFront
	S3 bucket

HTTPS api.bananas.openttd.org via ALB
	Forwarded to ECS openttd/content-api

HTTPS bananas.openttd.org via ALB
	Forwarded to ECS openttd/content-web

IPv4-TCP-3978 content.openttd.org via NLB
	Forwarded to ECS openttd/content-server

IPv6-TCP-3978 content.openttd.org via EC2
	Forwarded via proxy-protocol over IPv4 to NLB
	(NLB does not support IPv6)