# About "large file" and "resume download" on reverse proxy mode

**URL:** <https://www.ruby-forum.com/t/about-large-file-and-resume-download-on-reverse-proxy-mode/209505>\
**Category:** NGINX\
**Created:** [July 15, 2011, 7:39am UTC](https://www.ruby-forum.com/t/about-large-file-and-resume-download-on-reverse-proxy-mode/209505 "2011-07-15T07:39:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dubstep](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/cdc98d/32.png) [@dubstep](https://www.ruby-forum.com/u/dubstep)\
**Post date:** [July 15, 2011, 7:39am UTC](https://www.ruby-forum.com/t/about-large-file-and-resume-download-on-reverse-proxy-mode/209505/1 "2011-07-15T07:39:52Z")

</div>

Dear list,  
I am testing nginx with reverse proxy mode.  
I found that nginx download the file from upstream server to  
proxy\_temp\_path when I download a file from the reverse proxy server,if  
I stop and re-download,the nginx will download the file from upstream  
server again,and so on.  
The problem is when a large file on a site,someone could launch  
malicious multi-threaded connections to attack the reverse proxy server  
and upstream server.  
any configuration to limit it?

Another problem, when I pause and resume to download, and nginx has not  
finished download from upstream server,it would show the message:the  
server error.But when the file cached,it works fine.

Best

2011-07-15

chinix

---

<div class="post-metadata">

**Author:** ![chinix](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/35a633/32.png) [@chinix](https://www.ruby-forum.com/u/chinix)\
**Post date:** [July 15, 2011, 2:49pm UTC](https://www.ruby-forum.com/t/about-large-file-and-resume-download-on-reverse-proxy-mode/209505/2 "2011-07-15T14:49:54Z")

</div>

On 15 Jul 2011 06h39 WEST, [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> Dear list, I am testing nginx with reverse proxy mode. I  
> found that nginx download the file from upstream server to  
> proxy\_temp\_path when I download a file from the reverse proxy  
> server,if I stop and re-download,the nginx will download the file  
> from upstream server again,and so on. The problem is when a large  
> file on a site,someone could launch malicious multi-threaded  
> connections to attack the reverse proxy server and upstream server.  
> any configuration to limit it?

See [GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com · GitHub](http://wiki.nginx.org/HttpLimitReqModule) and  
[GitHub - nginxinc/nginx-wiki: ARCHIVED -- Source for the now archived NGINX Wiki section of https://www.nginx.com · GitHub](http://wiki.nginx.org/HttpLimitZoneModule).

— appa