Prevent reverse proxy from sending range headers to source server

[Robert Paprocki]

>From the docs (
http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_set_header):

If the value of a header field is an empty string then this field will not
be passed to a proxied server:

proxy_set_header Range "";


proxy_ignore_header is meant to handle response headers, not request headers

On Thu, Feb 4, 2016 at 5:38 PM, FSC <nginx-forum at forum.nginx.org> wrote:

> Hello everyone!
>
> I set up my reverse proxy to cache files stored at AWS S3. I want to
> minimize the amount of traffic generated at AWS.
>
> Many of the files are mp4s. Clients make GET requests with the range set. A
> video player may get multiple chunks of a file at once.
>
> How can I have the proxy server NOT send the client's Range header along to
> AWS S3? I want the cached version to be used. The file should only be
> revalidated after the set period of 30 days.
>
> So it seems like I would need something along proxy_set_header but
> something
> that unsets the header sent to the proxied server.
>
> E.g. proxy_set_header Range NULL
>
> The proxy_ignore_headers option won't take Range.
>
> I appreciate any help.
>
> Posted at Nginx Forum:
> https://forum.nginx.org/read.php?2,264362,264362#msg-264362
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160204/570a03b5/attachment.html>