On Sat, Jun 13, 2015 at 7:32 AM, Curtis <[email protected]> wrote: > > Will cloud front make the request claiming support for gzip? If so, it > should take care of the rest, surely? Specifically, serving it > uncompressed for those clients that don't support it. >
Cloudfront forwards the headers of the request from the client. With Vary: Content-Encoding there should be no problems. My understanding is the static-map is normally handed off to offload > threads [you have them configured, right?] so they don't take part in the > normal response routing any more, but also don't consume an app worker > thread/process. > No offloading ATM, and considering Cloudfront not even in the future. If I use: route = ^/static/(.) addheader:Cache-Control: public, max-age=2592000 this is added to the response, so routing is not bypassed. In my understanding the gzip transformation works only if Content-Length is not set, but static-map sets it. Regards. -- Davide Setti code: http://github.com/vad
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
