Optimize using the library with Nginx as a proxy to AWS S3

[davidfischer-ch]

Hello,

Many years ago I made some changes for the sole purpose of integrating this module into both personal and professional projects that are running on Amazon Web Services and using S3 as a backend for the media assets.

This module helped me to build a secured yet scalable and efficient assets storage by proxyfing S3 with Nginx.
The applications are offloading data transfers to Nginx thanks to X-Sendfile header.

In such a setup, trivial operations such as computing mime type or file size requires unnecessary roundtrips (and data transfer) from S3 to the servers. I investigated the issue and found a neat way to optimize such a setup.

Basically I had two means to optimize the storage :

1. Precompute values (e.g. mimetype and size) and store into the application's DB.
2. Let the backend (Nginx + S3) do their job (return HTTP 404 if file is missing, add Content-Type header, etc).

Actually there two projects running in production (Django and Flask) with this module (my version of it).

I would be glad to contribute to this repository and offer the opportunity to other users to use these features ...

Thank you for reviewing the changes.

Best Regards,

David Fischer