Welcome! Log In Create A New Profile

Advanced

Re: HTTP_HEADER parsing, Documentation implies $http_range should work.

Magdalena
July 17, 2009 05:18AM
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 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
>
>
Subject Author Posted

HTTP_HEADER parsing, Documentation implies $http_range should work.

Magdalena Glinkowski July 16, 2009 05:02PM

Re: HTTP_HEADER parsing, Documentation implies $http_range should work.

Maxim Dounin July 16, 2009 10:25PM

Re: HTTP_HEADER parsing, Documentation implies $http_range should work.

Magdalena July 17, 2009 05:18AM

Re: HTTP_HEADER parsing, Documentation implies $http_range should work.

Igor Sysoev July 17, 2009 05:49AM

HTTP_HEADER parsing, Documentation implies $http_range should work.

Magdalena July 16, 2009 10:22PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 191
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready