Azure CDN returning 404 while origin url doesn't

Question

I've created a cdn service and set the origin url to a azure website which runs iis-node that serves a NodeJS web application, when trying to access static resources the cdn always return 404 while the same pathname works when accessing the resource through the origin url,

anything that i might be missing here?

thanks!

Answer 1

Turns out it takes at least an hour until the content is being populated, during that time the CDN return 404.

Answer 2

Based on the article

A content delivery network (CDN) is a distributed network of servers that can efficiently deliver web content to users. CDNs store cached content on edge servers in point-of-presence (POP) locations that are close to end users, to minimize latency.

Azure Content Delivery Network (CDN) offers developers a global solution for rapidly delivering high-bandwidth content to users by caching their content at strategically placed physical nodes across the world

What you can do though to fasten the process is to just log in to Azure portal, go to the CDN profiles section, pick your CDN, And Click on Purge on the top menu. It should automatically update the content of the cache memory for your endpoint/s and you shouldn't wait hours. Hope it helps. Cheers

Answer 3

In case anyone else comes across this thread - I built an Azure CDN (Verizon Standard) and it took almost 24 hours for the images/files to pull up using the Endpoint Hostname.

Unfortunately, in my case I thought I was doing something wrong so I kept changing it which probably prolonged it. When I finally realized I did everything correct I decided to wait it out.