i just upped to .5 (using freebsd port), and have been finding a
bunch of errors/bugs.
access_log
'off' no longer turns the access log off. it now logs to a file
named off (relative to nginx config file / root )
i seem to be getting access_log and debug (error log) information
there. i'm not quite sure what is going on.
proxy
if i have a fastcgi proxy defined all proxy pass directives seem to
go that ip/port
whats very odd, is that php is set to spawn to 8888
location ~ .php$ {
fastcgi_pass 127.0.0.1:8888;location ~ .php$ {
fastcgi_pass 127.0.0.1:8888;
}
if that match is active at all in the nginx config, all proxy
passes go to 127.0.0.1:8888
location / {
proxy_pass http://127.0.0.1:8022;
}
will go to 127.0.0.1:8888 and cause an error
mod_proxy seems to not work at all otherwise.
there are a bunch more errors, but that seems to be the ones i can
figure out the most about
i can't figure out if this is specific to the FreeBSD port or nginx
in general.
In any case, if you are on FreeBSD, I STRONGLY suggest sticking to .4.14
also: it would be nice if there were a way to do a debug level for
mapping only. apache and lighttpd both support this.
ie:
request uri = x
try patterns y
matched to z
nginx has this support, but there seems no way to isolate it
2 messages in ru.sysoev.nginx.5 upgrade errors
.txt
