I can confirm this bug too. What I noticed is that eg. changes to
directive "proxy_intercept_errors on;" have no effect until you issue
a full restart.

ssehic@amd64:/home/ssehic$ /usr/local/sbin/nginx -V
nginx: nginx version: nginx/1.0.3
nginx: TLS SNI support enabled
nginx: configure arguments: --prefix=/etc/nginx
--conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx
--pid-path=/var/run/nginx.pid --lock-path=/var/nginx/tmp/nginx.lock
--http-client-body-temp-path=/var/nginx/tmp/client_body_temp
--http-proxy-temp-path=/var/nginx/tmp/proxy_temp
--http-fastcgi-temp-path=/var/nginx/tmp/fastcgi_temp
--http-log-path=/var/log/nginx/access.log
--error-log-path=/var/log/nginx/error.log --user=_nginx --group=_nginx
--with-http_ssl_module --with-http_stub_status_module
--with-http_perl_module --with-debug

ssehic@amd64:/home/ssehic$ uname -a
OpenBSD amd64.lab 4.8 GENERIC.MP#7 amd64

This worked just fine with 0.8.50 which I recently upgraded from.

Cheers,
Srebrenko

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx