I've found that the easiest , most accurate way of diagnosing cache related issues is to use the incredible rebot.org service. If you can point redbot at your nginx, and also at your back end, it will identify anything that prevenst the resource being cacehable. If your website isnt visible from the internet you can either install your own copy of redbot or use an ssh tunnell to make it visible temporarily.
The next approach si to run a debug version of nginx and to step by step unpick the setup to see whats broken. Peter I wopuld suggest begiining with a small filebefore then lovinto a laregr number On Jun 26, 2017, at 01:39 PM, deivid__ <nginx-fo...@forum.nginx.org> wrote: Hi, I currently get requests that are resolved with an external server to a file with X-Accel-Redirect: for example: /data/asd-asd-asd -> proxied to a backend -> resolves to file.xls /data/qqq-qqq-qqq -> proxied to a backend -> resolves to file.xls /data/123-123-123 -> proxied to a backend -> resolves to image.jpeg I want to cache the resulting files with nginx, as the initial access is very costly (they are accessed over the network). On first access they should be copied to a local cache, following requests should also go to the backend but actually serve the file from cache. My current config: https://zerobin.davidventura.com.ar/?0018df75a5d31f2c#Un5Eo10lo4eRnhY7ngQiHlSTErCVH/8zjRN+qS0JSl0= Note: The files are quite large (up to 4gb) I added the proxy_cache directives to both the requests path and the internal path but none of them are working. /cache/ is never populated, and the X-*-Cache headers are not present in the response Posted at Nginx Forum: https://forum.nginx.org/read.php?2,275138,275138#msg-275138 _______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
