OK. I was able to resolve it by doing a clean install of nginx. Dunno what the underlying issue was, but my hunch is I was logging to an a different location and the logs I was looking at were the default logs from nginx. Thanks anyway! On Mon, May 20, 2013 at 2:47 PM, Ramesh Muraleedharan <ramesh1987@gmail.com>wrote: > I've tried print() as well, and neither that nor ngx.log() have wby bhedia - Nginx Mailing List - English
I've tried print() as well, and neither that nor ngx.log() have worked as yet. On Mon, May 20, 2013 at 2:42 PM, Jader H. Silva <jaderhs5@gmail.com> wrote: > *ngx.print()* is only valid for r*ewrite_by_lua*, access_by_lua* and > content_by_lua*.* Maybe your looking for* print() > > ngx.log* should work though*. > * > > * > * > > > 2013/5/20 Ramesh Muraleedhby bhedia - Nginx Mailing List - English
Hi all, I've been experimenting with rewriting 'Set Cookie' headers in a nginx-reverse-proxy effort. The Set-Cookie rewrite doesn't seem to work yet, and more importantly, my log/print statements don't print to error_log as directed, making it very difficult to debug. http { server { access_log /home/bhedia/access.log; #error_log /home/bhedia/errors.log debug; error_log /home/bhby bhedia - Nginx Mailing List - English