CDN Forward HTTP Proxy
Currently we are only serving static content through CDN, it would be nice to serve dynamic content with cookies etc, where CDN kind of acts as a Forward HTTP Proxy instead of CDN. Benefit will be of multiplexing HTTP traffic to single host.
We need more details on what you are looking for regarding “multiplexing HTTP traffic to a single host” The CDN is built as a reverse proxy and can be used for both static and dynamic content. For dynamic content that you don’t want to be cached by the CDN you can either set the appropriate cache control header (e.g. max-age) or use the bypass cache capability in the rules engine in the Azure CDN Premium to control this for specific content. Long term we are working on enabling this capability also in Azure CDN Standard.
Akash Kava commented
Let's say I have a website located in US East cost, may or may not be hosted with Azure. And people access it by secure.myportal.com, every other static resource is already served by cdn, but dynamic user specific content is served from US East cost to every point in the world.
As an alternative, we can setup one different website in each Azure region and have all websites use connection string to SQL, which is not an ideal situation. This requires different endpoint name for each region for app service. This requires additional dns management to serve different cname based on location. Lots of work to make websites available on various locations.
Just like CDN, if each POP could serve as a proxy to my original website, each POP could keep open HTTP/2 connection and multiplex traffic of all end clients. This will significantly improve speed for end user as end user would be connecting to local POP and local POP would keep one persistent HTTP/2 connection with certain TTL.
Akash Kava commented
Let's say we have an web site, master.myapp.com that is hosted in US East region. CDN only benefits us for static content served without cookies. For users in different geographic regions master.myapp.com performs little slower (authenticated sessions etc). If there was cdn.myapp.com, which will route all traffic to master.myapp.com (including cookies, authenticated sessions). In same region connection to cdn.myapp.com would be quick, and if your nodes keep dns and keep alives to master.myapp, that would be superfast.