Re: Empty error and access log

evel & initiate kill command with USR1. Thanks in advance. Regards, Krishna Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285708,285726#msg-285726 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Empty error and access log

Hi Francis, Thanks for the reply. logrotate has been used to archive the nginx log files on daily basis from the machine and below is the configuration. Once it has been executed, the files would get zipped in gzip format and new files would get created (as killing the nginx PID, further the ngi

Re: Empty error and access log

Workaround: restarting nginx helps and logs getting generated. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285708,285709#msg-285709 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Empty error and access log

Dear Team, I have configured access_log and error_log at https block level and sometimes(like after log rotation), could see the logs are with 0 bytes (which means, nothing logged though it serves the requests and application is accessible). Any help would be appreciated to figure out the issue

Nginx - Rate limit when origin server response code is 401

Hello, I would like to limit access to my API endpoints when unauthorized requests (i.e. when origin server responds with 401 status code) are made but I wasn't able to find any information on how to go about this online. Is this possible using nginx? Please let me know. Regards, Kr

Re: Server very delayed in sending SYN/ACK

Hi Will, > * In the packet capture from the server, I see the SYN packet come in, then 3 more retransmits of that same syn come in before the server sent back the SYN/ACK. To me this indicates the issue in kernel or nginx side. Many times clients sends multiple SYN's. You can run wireshark to che

RE: secure and httponly cookies

, 8 March 2016, Krishna Kumar K K mailto:kris...@brocade.com>> wrote: I am able to modify the set-cookie header from the server to flag it secure. I am trying to do the same in the request header as well. Those flags are instructions to client. They don't have meaning on request heade

RE: secure and httponly cookies

Subject: Re: secure and httponly cookies On Mon, Mar 07, 2016 at 09:50:00PM +, Krishna Kumar K K wrote: Hi there, > I have tried exactly the same as in this page:- > > proxy_cookie_path / "/; secure; HttpOnly"; > > it sets the flags on the cookie in the response header,

RE: secure and httponly cookies

-IP $remote_addr; proxy_set_headerX-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_headerX-Forwarded-Proto $scheme; proxy_pass http:///; proxy_read_timeout 90; } } -Original Message- From: Krishna Kumar K K Sent: Monday, March 07, 2016 1:50 PM To: nginx@ngin

RE: secure and httponly cookies

I have tried exactly the same as in this page:- proxy_cookie_path / "/; secure; HttpOnly"; it sets the flags on the cookie in the response header, but when I refresh the page, it is sending the cookies in the requests header without these flags, it just resets it. Thank

This webpage has a redirect loop (ERR_TOO_MANY_REDIRECTS)

proxy_set_header X-Forwarded-Proto $scheme; proxy_pass http:///; proxy_read_timeout 90; } } Please help. Thanks, Krishna ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

pcre_exec() failed: -10

; error when it encounters the regex. Any pointers, please? Please refer below for more details. TIA, Krishna! *1. from nginx config* if ($args ~ "(*UTF8)^.*[^\x21-\x7E].*$") { return 404; } *..* *2. from access log:* 54.169.206.188 [26/Jan/2016:20:29:10 /search?userQuery=T