Support CDN module

In researching this, I also found this little tidbit that could be helpful: http://www.nomitor.com/blog/2010/11/10/gzip-support-for-amazon-web-servi...

According to that link, in order for Nginx to support Amazon Cloudfront delivering gzipped content, the gzip_http_version needs to be set to 1.0. Now that was 2 years ago, so it could have changed, but I thought it was worth noting here, just in case.

-Joseph

Sweet deal! Thanks for working on this.

I tried using it, but there were two problems. First, the rewrite wasn't quite right, but I think I managed to fix it. There are actually two "directories" added after "farfuture", not just one. Also, they weren't just alphanumeric, but also could contain some symbols. I was able to come up with two examples of different types of generated URLs that should be forwarded. Here is an example of each:

http://my.domain.com/cdn/farfuture/x5E_sG2mohSfzRmYQncvKqY2Nfc3UHdifrybk5HaR7Vs/mtime:43444553996/sites/my.domain.com/files/js/js_-ee4lnX3FpHqxxULJlddn_OVc29Ghc7WfGJL23OaFI0.js
http://my.domain.com/cdn/farfuture/gilZCzQfySRkP1HNe5Xndvw9amSD9yFPSjWJh0hni8/drupal:7.14/misc/feed.png

And here is the new rewrite that I believe works for both kinds:
rewrite ^/cdn/farfuture/[^/]+/[^/]+/(.+)$ /$1 last;

But the other problem is that the third "location" block (with css|js|etc) isn't working right. It is generating 404 errors. If I remove it, the 404 errors go away, but obviously the headers don't get added. Any idea how to fix it? I tried changing the rewrite flag above from "last" to "break" but it didn't make a difference. (I couldn't fully grok the documentation for nginx rewrite flags, but it seemed like we might want "break".) I also tried moving the try_files line after the block and inside the block, but I was just taking stabs in the dark at that point, so I thought I'd come back here for more help.

Thanks again,
-Joseph

Just to be clear, that means I'm using the following config:

###
### CDN Far Future expiration support.
###
location ^~ /cdn/farfuture/ {
  location ~* ^/cdn/farfuture/ {
    access_log off;
    expires    epoch;
    limit_conn gulag 88;
    rewrite    ^/cdn/farfuture/[^/]+/[^/]+/(.+)$ /$1 last;
    add_header ETag "";
    add_header Vary "Accept-Encoding";
    add_header Accept-Ranges "bytes";
    add_header Cache-Control "private, must-revalidate, proxy-revalidate";
    add_header X-Header "CDN Generator 1.0";
    set $nocache_details "Skip";
    try_files  $uri @drupal;
  }
}

This is the part I had to remove:

    location ~* \.(?:css|js|svg|ico|gif|jpg|jpeg|png|otf|ttf|eot|woff|flv|swf)$ {
      add_header Cache-Control "max-age=290304000, no-transform, public";
      add_header Last-Modified "Wed, 20 Jan 1988 04:20:42 GMT";
      expires    max;
    }

I still haven't been able to figure out how to get it to work. I just get 404 errors when I put it back in. Looking at the nginx documentation, I can't figure out why. I'm sure I'm missing something obvious...

It actually seems to do a pretty good job, even without it, but obviously it would be better if we could get that part working too.

-Joseph

LOL. Nope, I can't test it anymore, since we moved all our sites onto your hosting. :)

Actually, don't you run all the sites on your servers on HEAD? Maybe I could do testing still... Let me know.

-Joseph