Forgive me if this has been covered before, but I didn't see anything while searching. I have a server setup similar to: server { listen 80; server_name domain.com someotherdomain.com somethirddomain.com; rewrite "^(.*)$" http://www.domain.com$1 permanent; } server { listen 80; server_name www.domain.com *.domain.com; server_name_in_redirect off; &lby KyleChristensen - Nginx Mailing List - English
That seems to have stopped the segfaults. I'll report back if I run into anything fishy. Thanks for the quick response!by KyleChristensen - Nginx Mailing List - English
Igor, I've got 0.8.48 installed, and the dma_code and area_code are working well. however, when I include $geoip_region_name via: fastcgi_param GEOIP_REGION $geoip_region; fastcgi_param GEOIP_REGION_NAME $geoip_region_name; fastcgi_param GEOIP_CITY $geoip_city; fastcgi_param GEOIP_DMA_CODE $geoip_dma_code; fastcgi_param GEOIP_AREA_CODEby KyleChristensen - Nginx Mailing List - English
That's great news Igor, thanks for the quick work! GEOIP_REGION_NAME is slightly different than GEOIP_REGION, if I dump $_SERVER, you can see: => CA => California I'm not sure about abroad, but here in the states region maps to a state abbreviation, and region_name is the full name of the state.by KyleChristensen - Nginx Mailing List - English
Igor, Sorry for resurrecting this old thread, but I've been working on deploying Nginx, and I noticed that the GeoIP City module is missing a couple of variables that are set by the equivalent mod_geoip module for Apache. The variables in question (as set by mod_geoip) are: GEOIP_ADDR GEOIP_REGION_NAME GEOIP_DMA_CODE GEOIP_AREA_CODE I'm not certain what information you'd need to addby KyleChristensen - Nginx Mailing List - English