The reply I received from NetDNA after supplying the same information as I did here is as follows:
"Too many redirects" is a legit message in this scenario - example: You are redirecting domain.com/file.jpg TO cdn.domain.com/file.jpg ---> request comes to CDN and CDN neds to cache this file from origin so it tries to fetch from origin from location "domain.com/file.jpg" ---> request comes to origin and redirect rule you made redirects this request back to CDN <--- this is where infinite loop starts.
This is not a proper way to implement CDN as you have to monitor who is requesting your origin file so you could know whether it's a request you want to redirect or not. The best way to handle this is to monitor our anycast IPs and redirect everything except for those ips:
108.161.176.0/20
70.39.132.0/24
92.60.240.208/29
92.60.240.217/29
216.12.211.60/32
216.12.211.59/32
If you want to implement CDN this way, we can't support that implementation as we don't really encourage our client to use this type of implementation. The reason is quite simple: We are going to add new IP block that has to be white listed and until you make update for your redirects rule you'll be pushing infinite redirects to our servers causing service not to work until you add new block as well.
