Can confirm @bloodwin’s report. Plugin doesn’t appear to be working with nginx. Headers are showing 404. Works fine on other sites using apache. This is a pity because it’s a good lightweight plugin and, with more webmasters switching across to nginx because of its performance benefits, it would have been good for this to continue working.
My apologies. The plugin does work with nginx. I made a stupid error in my config file. Staying up too late!
@bloodwin – if you’re still having problems, post your nginx config file (with all of your identifying details removed) and will try and help sort out issue.
Hello, @iamrobbo!
Here’s my config. Will be very thanxfull for any help, i’m newbe in nginx.
server {
listen 80; ## listen for ipv4; this line is default and implied
root /var/www/mysite;
index index.html index.htm index.php;
# Make site accessible from http://localhost/
server_name mysite.ru www.mysite.ru;
access_log /var/log/nginx/mysite.access.log combined;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
proxy_pass http://127.0.0.1:8080/;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
client_max_body_size 10m;
proxy_connect_timeout 90;
}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
location ~ /\.ht {
deny all;
}
#Static content
location ~* ^.+\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|js)$ {
root /var/www/mysite;
}
}
