Dear all,
We have been using nginx as a reverse-caching-proxy for quite a time now and we face an issue.
We server big files (200MB+) and we sometimes have a traffic spike on the backend server because of multiple requests going to the backend to fetch the same file.
1) if we use proxy_cache_lock, what happens if we set the timeout quite high on the users' browsers? download does not start until the timeout is reached?
2) best scenario would be: how to make nginx use what it has already downloaded for the first request and pass it over the second request?
Thanks in advance for your feedback!
We have been using nginx as a reverse-caching-proxy for quite a time now and we face an issue.
We server big files (200MB+) and we sometimes have a traffic spike on the backend server because of multiple requests going to the backend to fetch the same file.
1) if we use proxy_cache_lock, what happens if we set the timeout quite high on the users' browsers? download does not start until the timeout is reached?
2) best scenario would be: how to make nginx use what it has already downloaded for the first request and pass it over the second request?
Thanks in advance for your feedback!