This being worked on? Hard to debug ipv6 at times without use of IPV6 address in browser... Dan.by syle - Nginx Mailing List - English
Normally how I setup nginx is to proxy php/perl to apache sitting on port 81, for ipv6 its also a proxy pass for perl/php to some upstream local ipv4 address. For ipv6 when typing in a domain in browser utilizing a ipv6 address all works just fine, but if I use a IPV6 IP address in the browser I get: 400 Bad syntax. this is only for the proxy to apache for php/perl requests. Can somby syle - Nginx Mailing List - English
Sergey: I will just do following for now, so maybe overwriting fastcgi_params might not be such a bad thing on freebsd since we will always get a new copy of anything that changes automatically, i've just thrown the geoip values in another include as follows: location ~ \.php$ { #fastcgi_pass 127.0.0.1:9000; fastcgi_pass unix:/tmp/cgi2.sock; fastcgi_indexby syle - Nginx Mailing List - English
Unfortunately the location directive only works in server context, so fastcgi_param SCRIPT_FILENAME is always going to loose any http context defined vars for executing php and perl scripts, basically where they are needed. Would be nice to be able to set location in http context for those perl and php scripts as I have them, making them server wide for vhosts. I'll take your other suggestiby syle - Nginx Mailing List - English
Actually I'll post one of my server directives so we can see if there is any inheritance problems like you suggested, i have about 50 server directives the same as this: ( I know it seems quite bloated but I didn't read any way I could set php and perl/cgi scripts outside of server directivesfor all the vhosts) server { listen 80;#bind to ipv4 listen [::]:80; #bindby syle - Nginx Mailing List - English
It is assumed when we use REALIP_MODULE and purposely set REMOTE_ADDR to real ip of our proxies in front that this is the real client IP that GEOIP should be using. example: proxy of nginx in front of a fastcgi nginx. Proxy config: proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarby syle - Nginx Mailing List - English
Thankyou for repliies, as far as freebsd guy, reading your patch just suggests not removing fast fastcgi_params file which would be a nice commit till this is resolved. Maxim: I was doing strictly in http context as module was documented nothing else and it was not recogised at all ie: http { #GEOIP, can parse ENV headers now for where they are located :) geoip_city /usrby syle - Nginx Mailing List - English
There is a problem with current 0.8.x release of GEOIP although I assume it has always not worked, where these variables: fastcgi_param GEOIP_CITY_COUNTRY_CODE $geoip_city_country_code; fastcgi_param GEOIP_CITY_COUNTRY_CODE3 $geoip_city_country_code3; fastcgi_param GEOIP_CITY_COUNTRY_NAME $geoip_city_country_name; fastcgi_param GEOIP_REGION $geoip_region; fastcgi_param GEOIP_CITY $geoip_city;by syle - Nginx Mailing List - English