Traditionally raster maps were hosted from multiple subdomains, like tile1, tile2, tile3.domain.com, etc.
I guess with HTTP/2 this might be less important, but for example Mapbox still hosts from a.tiles.mapbox.com and b.tiles.mapbox.com, so still there must be some reason for doing it.
For example, this is how mapbox-streets-v8 looks like:
OK, based on this article this technique is totally not needed or recommended since HTTP/2. Probably Mapbox uses it to support legacy clients or something similar.
Traditionally raster maps were hosted from multiple subdomains, like tile1, tile2, tile3.domain.com, etc.
I guess with HTTP/2 this might be less important, but for example Mapbox still hosts from
a.tiles.mapbox.com
andb.tiles.mapbox.com
, so still there must be some reason for doing it.For example, this is how mapbox-streets-v8 looks like:
Please allow specifying domains to be used in the
tiles
key of the auto-generated services JSON.Ideally it'd be something like this in an env var:
SUBDOMAINS
: "a.tiles.mapbox.com,b.tiles.mapbox.com"