Hi All,
We’re using the CDN to deliver json files to the client. The client request around 18-30 json files simultaneously. I know that this can appear
as an awkward solution but the application is map based and the client loads a json file for each map tile that is loaded. Due to the 6 connections per host limit in most browsers, see
link, the json files are loaded in sequence. From a performance perspective we would like the client to load the json
files from multiple hosts in order to trick the browser to execute all requests in parallel (simultaneously), a.k.a parallelize downloads across hostnames, see
link
and link.
To accomplish our goal we’ve set up a custom domain for the hosted service cdn endpoint according to
link
and link.
Let’s say our custom domain is cdn.ourdomain.com, now we have two domains to our cdn namely; cdn.ourdomain.com and <id>.vo.msecnd.net (azure cdn host). But we want even more domains and we don’t want to expose the vo.msecnd.net host to the
client. We moved ahead and created five new host names (CNAMES); cdn1.ourdomain.com, cdn2.ourdomain.com, cdn3.ourdomain.com, cdn4.ourdomain.com and cdn5.ourdomain.com which all points to cdn.ourdomain.com, the configured custom domain for the cdn endpoint.
Nslookup for cdn1.ourdomain.com gives the following result:
C:\Windows\system32>nslookup cdn1.ourdomain.com
Server:
x
Address:
192.168.40.1
Icke-auktoritärt svar:
Namn:
<id>.vo.msecnd.net
Addresses:
94.245.71.145
94.245.71.144
Aliases:
cdn1.ourdomain.com
cdn.ourdomain.com
BUT the cdn itself returns a 400 bad request for all cdnX.ourdomain.com requests. We know that this is probably due to the fact the only
configured and authorized custom domain is cdn.ourdomain.com, but is there a known work around to parallelize cdn requests across hostnames?
BR,
Max.