HTTP_HEADER parsing, Documentation implies $http_range should work.
is at rambler-co.ru
Fri Jul 17 13:49:10 MSD 2009
On Fri, Jul 17, 2009 at 02:18:30AM -0700, Magdalena wrote:
> 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.
You do not need to pass HTTP_RANGE specially, it is passed by default.
> On Thu, Jul 16, 2009 at 7:25 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> > Hello!
> > On Thu, Jul 16, 2009 at 02:02:40PM -0700, Magdalena Glinkowski wrote:
> > > http://wiki.nginx.org/NginxHttpCoreModule#.24args
> > >
> > > 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
More information about the nginx