<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>What netdna said is sensible and I imagine any cdn would say the same. Ultimately the ball is in your court.</div><div><br></div><div>If you want to use a CDN (and it's not compulsory) then change your app so that the image links are absolute links with the cdn domain name. There's no good reason for nginx to have any part of this<br><br>Sent from my iPhone</div><div><br>On Mar 21, 2013, at 6:49 PM, "toddlahman" <<a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a>> wrote:<br><br></div><blockquote type="cite"><div>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="MS Exchange Server version 6.5.7654.12">
<title>Re: Too Many Redirects - CDN Rewrite Rule</title>
<!-- Converted from text/plain format -->
<p><font size="2">The reply I received from NetDNA after supplying the same information as I<br>
did here is as follows:<br>
<br>
"Too many redirects" is a legit message in this scenario - example: You are<br>
redirecting <a href="http://domain.com/file.jpg">domain.com/file.jpg</a> TO <a href="http://cdn.domain.com/file.jpg">cdn.domain.com/file.jpg</a> ---> request<br>
comes to CDN and CDN neds to cache this file from origin so it tries to<br>
fetch from origin from location "<a href="http://domain.com/file.jpg">domain.com/file.jpg</a>" ---> request comes to<br>
origin and redirect rule you made redirects this request back to CDN <---<br>
this is where infinite loop starts.<br>
<br>
This is not a proper way to implement CDN as you have to monitor who is<br>
requesting your origin file so you could know whether it's a request you<br>
want to redirect or not. The best way to handle this is to monitor our<br>
anycast IPs and redirect everything except for those ips:<br>
<br>
108.161.176.0/20<br>
70.39.132.0/24<br>
92.60.240.208/29<br>
92.60.240.217/29<br>
216.12.211.60/32<br>
216.12.211.59/32<br>
<br>
If you want to implement CDN this way, we can't support that implementation<br>
as we don't really encourage our client to use this type of implementation.<br>
The reason is quite simple: We are going to add new IP block that has to be<br>
white listed and until you make update for your redirects rule you'll be<br>
pushing infinite redirects to our servers causing service not to work until<br>
you add new block as well.<br>
<br>
Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,237609,237661#msg-237661">http://forum.nginx.org/read.php?2,237609,237661#msg-237661</a><br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</font>
</p>
</div></blockquote></body></html>