In what format is $binary_remote_addr? Test shows network byte order (big-endian), but is that guaranteed? English wiki doesn't say, and my Russian leaves much to be desired. helenby helen - Nginx Mailing List - English
There is information available to log by the fastcgi backend which is not available to nginx, and vice versa (e.g., $body_bytes_sent). I need some way to match these two logs together after the fact. This necessarily implies a quasi-GUID guaranteed to be unique to each request. Preferably it should be something generated by nginx and fed to backend through a fastcgi_param (or for those using prby helen - Nginx Mailing List - English
On Tue, 02 Nov 2010 18:17:54 -0400, Frank Church <vfclists@gmail.com> wrote: > I have spent a few hours trying to debug 'No input file specified' errors > until I realized that the script_filename must be specified in upper case > > ie, > > fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; > > rather than > > fastcgi_param script_fby helen - Nginx Mailing List - English
On Wed, 20 Oct 2010 21:57:32 -0400, helen <nginx-forum@nginx.us> wrote: > On Wed, 20 Oct 2010 21:23:46 -0400, Pierre-Marie Baty wrote: > >> When the URL is Latin-1 encoded, the request sent is : GET >> /%e9t%e9-2008.jpg ----> nginx resolves this to "été-2008.jpg", the > file >> is served, OK >> When the URL is UTF-8 encoded, the requeby helen - Nginx Mailing List - English
On Wed, 20 Oct 2010 21:23:46 -0400, Pierre-Marie Baty <baty.pm@hotmail.fr> wrote: > When the URL is Latin-1 encoded, the request sent is : GET > /%e9t%e9-2008.jpg ----> nginx resolves this to "été-2008.jpg", the file > is served, OK > When the URL is UTF-8 encoded, the request sent is : GET > /%C3%A9t%C3%A9-2008.jpg ----> nginx resolves this to &by helen - Nginx Mailing List - English
Works for me. $ /usr/local/bin/nginx -v nginx version: nginx/0.8.53by helen - Nginx Mailing List - English
On Sun, 17 Oct 2010 10:36:42 -0400, Ilan Berkner <iberkner@gmail.com> wrote: [...] > The above code works as expected, but I would like to do something like > this: > > location / { > if not 1.1.1.1 or 1.1.1.2 or 1.1.1.3 do a 301 redirect to > www.domain.com(with request uri) > } > > is this possible? Use the nginx geo module http://wiki.nginx.org/by helen - Nginx Mailing List - English