I have a working server running apache (mod_php) with nginx in reverse proxy and this is working OK (I am sure it could be improved!). I want to migrate this server to nginx with php-fastcgi (ultimately php-fpm but that would require an upgrade) but not in one go in case it all falls over and there are a few sites which still require apache for .htaccess/password issues. This would mean runnby Loggy - Nginx Mailing List - English
Not every GoogleBot enquiry is blocked which is a puzzle. But enough to render the page rank n/a. I have tried to add a trailing "/" after the docroot as would be required by the alias command. I am also trying to remove the "/" from the redirect as well as the "/" in the substitution so it is: server { listen 80; server_name mydomain.com; rewby Loggy - How to...
I have nginx 1.2.4 as a reverse proxy to apache2 and WordPress and this runs very sweetly. However today's upgrade in Google Page Ranks, far from promoting the various sites on my server, have set them to P/R=n/a. When I look at Webmaster Tools, I see that all recent scans have resulted in a 403 Access Denied result. But I cannot see why this should be. It is the usual setup with the purgby Loggy - How to...
The comment issue remains even with the WordPress Nginx proxy cache integrator plugin activated and the comments approved. They are not visible until the page of posts has expired.:( The plugin sets X-Accel-Expires to 0 where wordpress_comment_author or wordpress_wp-postpass cookies are set, thus switching off caching for that page and renewing the cache copy.by Loggy - Nginx Mailing List - English
Actually it's more serious than just the image. If you add a new comment when not logged in, the whole post with the new comment is entered into the cache and served OK. But an immediate additional comment added is not served because the cache hasn't expired. The comment count is also not updated. I have tried adding the Nginx proxy cache integrator which adds effectively expires the cachby Loggy - Nginx Mailing List - English
There are many attractions of Nginx as a front-end to Apache for WordPress - not least the retention of permalink facilities. I have been trying this for some time now and, when it works, the performance is certainly excellent. However there is one problem with all the configurations I have been trying and that is the header image in the default WordPress twentyeleven theme when not logged iby Loggy - Nginx Mailing List - English