Problem using S3

Testing PRIVATE_STORAGE_S3_REVERSE_PROXY = True. It saves the files properly on S3, yet, when retrieving the file, when it tries to access the django sever view, it gives 404. Do I have to configure a reverse proxy with apache/nginx/caddy or the django server view actually fetches the object from S3 and proxies to the client?

[lorinkoz]

Possible problem: In django, I am hosting the reverse proxy on the url /file/... In the S3 bucket, the file folder does not exist.

Assuming private_file is an instance of a FieldFile returned by accessing a private file, if I do:

private_file.storage.exists(private_file.path) it raises SuspiciousOperation, as path is prefixed with /file. Then, if I manually remove the /file part, the storage returns True. As I said before, I can private_file.read() and private_file.size without any problem.

[vdboor]

Hi, the while point of the PRIVATE_STORAGE_S3_REVERSE_PROXY is to let Django retrieve the file, and serve it. Thus, Django becomes a proxy for the S3 file. I can’t really diagnose what’s happening here. Maybe some bucket policy prevents the file from being downloaded? For some reason Django doesn’t seem to be able to fetch the file.