# Force range request on proxy server

**URL:** <https://www.ruby-forum.com/t/force-range-request-on-proxy-server/236016>\
**Category:** NGINX\
**Created:** [July 31, 2013, 4:31am UTC](https://www.ruby-forum.com/t/force-range-request-on-proxy-server/236016 "2013-07-31T04:31:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![addis\_a](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/c4cdca/32.png) [@addis\_a](https://www.ruby-forum.com/u/addis_a)\
**Post date:** [July 31, 2013, 4:31am UTC](https://www.ruby-forum.com/t/force-range-request-on-proxy-server/236016/1 "2013-07-31T04:31:58Z")

</div>

We used amazon S3 as upstream server. And it does not serve  
‘Accept-Ranges:  
bytes’ as respond header. So the nginx proxy server will not serve range  
response even if the content has been completely cached on the proxy  
server.  
We tested on a upstream server that do serve ‘Accept-Ranges: bytes’ as  
respond header. And proxy server was working proper by servering range  
respond.  
Is that the default behavior for nginx proxy. Is there a way to  
overwrite  
it.

Posted at Nginx Forum:

> **[force range request on proxy server](https://forum.nginx.org/read.php?2,241394,241394#msg-241394)**
>
> We used amazon S3 as upstream server. And it does not serve 'Accept-Ranges: bytes' as respond header. So the nginx proxy server will not serve range response even if the content has been completely cached on the proxy server. We tested on a upstream...