<div>At this time we're delivering static content, in particular, audio files ~5K in size directly through our server, for a number of reasons, we're looking at moving delivery of these files to a remote storage / CDN facility.</div>
<div><br></div><div>Question re. URL requests for these files. Currently, these file are served through a request like this: <a href="http://www.ourdomain.com/sounds/a/alpha.mp3">http://www.ourdomain.com/sounds/a/alpha.mp3</a>. If we switched to a remote storage / CDN solution, the URL of course would change to something else. There are 2 options ( I think ):</div>
<div><br></div><div>1. Modify the application code to make the the call directly to the new URL.</div><div><br></div><div>2. Instruct Nginx through a location clause to redirect such traffic to another URL, for example:</div>
<div><br></div><div>location /sounds/*.mp3 {</div><div> rewrite <a href="http://www.cdn.com/$1">http://www.cdn.com/$1</a> ...</div><div>}</div><div><br></div><div>Is there a preferred way or does it matter? I guess the first option would probably be preferred as it further reduces the work load done by the server, even as simple as parsing the URL... Any thoughts / suggestions would be appreciated.</div>
<div><br></div><div>Also, does anyone have a recommendation / experience with any particular remote storage / CDN such as Rackspace CloudFile, Amazon S3, Limelight, CacheFly, etc?</div><div><br></div><div>Thanks</div>