HTTP_HEADER parsing, Documentation implies $http_range should work.

Magdalena theglobeisnowdigital at
Fri Jul 17 13:18:30 MSD 2009

Thank you for your response. Strange it didnt appear to work in practice.
I used curl to send the test request, and curl interpreted it correctly
based on its trace log.

I am not having any issues with any other getparam variable accesses except
this one.
My fastcgi_params file declares mapping to be HTTP_RANGE $http_range and the
result I get is null char
from the local request state environment.

On Thu, Jul 16, 2009 at 7:25 PM, Maxim Dounin <mdounin at> wrote:

> Hello!
> On Thu, Jul 16, 2009 at 02:02:40PM -0700, Magdalena Glinkowski wrote:
> >
> >
> > In the documentation above for the http_HEADER section, their is
> implication
> > that if I want "Range" from header,
> > I use "http_range" as the value, is this correct?
> Yes, $http_range variable will give you value of Range header from
> http request.
> Maxim Dounin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the nginx mailing list