On 1 Jun 2011 13h00 WEST, ngin...@nginx.us wrote:

location / { rewrite ^/(.*)$ /site/redirect?u=$1; }

location /site { location
/site/.*\.(?:xml|mp4|ttf|css|rss|atom|js|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|doc|xls|exe|ppt)$ expires max; access_log off; log_not_found off;

} location /site/private { auth_basic "Restricted"; auth_basic_user_file
/home/MYDOMAIN/.htpasswds/public_html/site/private/passwd; <fastcgi block here> }

location /site/wordpress { ## Regular PHP processing. location ~ ^/site/wordpress/(?<script>.+\.php)(?<path_info>.*)$ { include fastcgi.conf; ## The fastcgi_params must be redefined from the ones ## given in fastcgi.conf. No longer standard names ## but arbitrary: named patterns in regex. fastcgi_param SCRIPT_FILENAME $document_root$script; fastcgi_param SCRIPT_NAME $script; fastcgi_param PATH_INFO $path_info; ## Passing the request upstream to the FastCGI ## listener. fastcgi_pass unix:/dev/shm/php5-fpm.MYDOMAIN.sock;; } } }

location /site/redirect { <fastcgi block here> }

## you need a try_files directive here but your "desired" config is ## quite confusing and I don't know what you need/want. Perhaps:

try_files $uri $uri/ /site/wordpress; ## ??? }

For the fastcgi block use nested locations and named captures like the above example, always prefixing the regex with the outer location string, like in the /site/wordpress location.

--- appa