Re: HUP signal to nginx doesn't work Ubuntu14

: HUP signal to nginx doesn't work Ubuntu14 Hello! On Wed, Jun 03, 2015 at 05:06:57PM -0500, Kunal Pariani wrote: Hello, Am seeing an issue while sending HUP signal to nginx (for config reload) on Ubuntu14. It just kills the master process doesn't start the new worker processes. The same

HUP signal to nginx doesn't work Ubuntu14

Hello, Am seeing an issue while sending HUP signal to nginx (for config reload) on Ubuntu14. It just kills the master process doesn't start the new worker processes. The same works just fine on CentOS 6.6 64-bit $ ps -eaf | grep nginx zimbra 10860 1 0 16:05 ? 00:00:00 nginx: master process

nginx page caching not working for responses with valid (rfc 1123 compliant) Expires header

Hello, I am on nginx-1.7.1 trying to use nginx's page caching feature but run into an issue for responses with a valid 'Expires' header which seem to be in the correct rfc 1123 compliant format. Nginx somehow doesn't like it hence doesn't cache such responses. Is this a bug ?

Re: $upstream_addr containing the same ip twice

the same ip twice Hello! On Thu, Feb 19, 2015 at 08:49:33AM -0800, Kunal Pariani wrote: I have just one server configured with a single Ip address but I still see this. The example case mentioned isn't the only case when this can happen legitimately. -- Maxim Dounin http://nginx.org

Re: $upstream_addr containing the same ip twice

I have just one server configured with a single Ip address but I still see this. Thanks -Kunal On Feb 19, 2015 5:05 AM, Maxim Dounin mdou...@mdounin.ru wrote: Hello! On Wed, Feb 18, 2015 at 09:03:47PM -0600, Kunal Pariani wrote: Hello, I have just 1 backend server being reverse-proxied

$upstream_addr containing the same ip twice

Hello, I have just 1 backend server being reverse-proxied through nginx. The access log lists this one request for which the $upstream_addr has the same ip:port twice. Is this a bug ? :::10.255.255.248:51947 - - [18/Feb/2015:19:52:43 -0600] GET / HTTP/1.1 302 454 - Mozilla/5.0

Re: monitor upstream IP addr changes without using nginx's resolver

Sorry am new to Lua but can you plz explain how this upstream status control will help with this issue. How can i query for the upstream ip after every certain time interval and reconfigure nginx if there's a change detected ? The reason for not using nginx's resolver here is that i have to

Re: resolver directive doesn't fallback to the system DNS resolver

Is there already a patch for this ? I am not completely sure of how to make the nginx resolver (in ngx_resolver.c) fallback to libresolv automatically and if this not trivial enough, i just might read the resolvers from /etc/resolv.conf and provide it to the 'resolver' directive. Any

Re: resolver directive doesn't fallback to the system DNS resolver

Thanks Yichun Zhang.. - Original Message - From: Yichun Zhang (agentzh) agen...@gmail.com To: nginx@nginx.org Sent: Monday, January 12, 2015 2:19:08 PM Subject: Re: resolver directive doesn't fallback to the system DNS resolver Hello! On Mon, Jan 12, 2015 at 1:48 PM, Kunal Pariani wrote

Re: resolver directive doesn't fallback to the system DNS resolver

). Is there a way to achieve this ? Thanks -Kunal From: Francis Daly fran...@daoine.org To: nginx@nginx.org Sent: Wednesday, January 7, 2015 3:14:17 PM Subject: Re: resolver directive doesn't fallback to the system DNS resolver On Mon, Jan 05, 2015 at 05:04:52PM -0600, Kunal Pariani wrote: Hi

Re: resolver directive doesn't fallback to the system DNS resolver

Ping.. Thanks -Kunal From: Kunal Pariani kpari...@zimbra.com To: nginx@nginx.org Sent: Monday, January 5, 2015 3:04:52 PM Subject: resolver directive doesn't fallback to the system DNS resolver Hello, I am looking at how to use nginx's resolver directive (http://nginx.org/en/docs/http

resolver directive doesn't fallback to the system DNS resolver

Hello, I am looking at how to use nginx's resolver directive (http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver) to address this one issue i am facing. I have a host for which there is already an entry in the system DNS resolver (verified using nslookup/dig) but when i specify

Re: [PATCH] SSL support for the mail proxy module

Hello, Any reason for this patch not being committed upstream yet ? Thanks -Kunal From: Franck Levionnois flevionn...@gmail.com To: nginx-devel nginx-devel@nginx.org, Kunal Pariani kpari...@zimbra.com Sent: Tuesday, October 21, 2014 12:59:04 AM Subject: Re: [PATCH] SSL support

Re: Support for ssl_certificate_dir ?

444 on this one too ? Thanks -Kunal On Wed, Oct 8, 2014 at 2:31 PM, Kunal Pariani kpari...@zimbra.com wrote: Hello, Currently nginx doesn't have the capability to define the directory containing all the ssl certificates. This requires all the chained certificates need to be munched together

Re: Support for ssl_certificate_dir ?

Thank you. -Kunal - Original Message - From: Maxim Dounin mdou...@mdounin.ru To: nginx-devel nginx-devel@nginx.org Sent: Monday, October 13, 2014 1:17:26 PM Subject: Re: Support for ssl_certificate_dir ? Hello! On Mon, Oct 13, 2014 at 12:41:20PM -0700, Kunal Pariani wrote: 444

Re: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp)

Any responses on this please ? Thanks -Kunal - Original Message - From: Kunal Pariani kpari...@zimbra.com To: nginx-devel nginx-devel@nginx.org Sent: Wednesday, September 24, 2014 4:14:32 PM Subject: Re: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp) Some comments

Support for ssl_certificate_dir ?

Hello, Currently nginx doesn't have the capability to define the directory containing all the ssl certificates. This requires all the chained certificates need to be munched together in the right order in a single file and specified using the ssl_certificate directive

Re: [PATCH] Add 'version' parameter for http upstream server directive

: Thursday, September 18, 2014 4:00:54 AM Subject: Re: [PATCH] Add 'version' parameter for http upstream server directive Hello! On Wed, Sep 17, 2014 at 05:59:23PM -0500, Kunal Pariani wrote: # HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1410994128 18000 # Wed Sep

Re: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp)

Sent: Thursday, September 18, 2014 4:00:32 AM Subject: Re: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp) Hello! On Wed, Sep 17, 2014 at 03:49:50PM -0500, Kunal Pariani wrote: Hello, This patch adds separate mail parsing states per protocol (imap/pop/smtp), specific error codes

[PATCH] Update mail parsing to be per protocol (imap/pop/smtp)

# HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1410986530 18000 # Wed Sep 17 15:42:10 2014 -0500 # Node ID dfc11aa2a98e697a562b2aee092a77e3dc13f55a # Parent 65988e6762de9c2c98f5f028fddecf45bc05a913 Update mail parsing to be per protocol (imap/pop/smtp) diff -r

Re: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp)

heavily tested. Thanks -Kunal - Original Message - From: Kunal Pariani kpari...@zimbra.com To: nginx-devel nginx-devel@nginx.org Sent: Wednesday, September 17, 2014 1:45:14 PM Subject: [PATCH] Update mail parsing to be per protocol (imap/pop/smtp) # HG changeset patch # User Kunal Pariani

[PATCH] Add 'version' parameter for http upstream server directive

# HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1410994128 18000 # Wed Sep 17 17:48:48 2014 -0500 # Node ID 1cad46e7189fc43d50a24735f61793f710f78967 # Parent dfc11aa2a98e697a562b2aee092a77e3dc13f55a Add 'version' parameter for http upstream server directive diff -r

[PATCH] SSL support for the mail proxy module

# HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1410850478 18000 # Tue Sep 16 01:54:38 2014 -0500 # Node ID b35a5391bef67f79f7a099c0cb868477b9abeb43 # Parent e3016ee8dba396614f28a3644996b8cc6de8f9e3 SSL support for the mail proxy module diff -r e3016ee8dba3 -r

Re: [PATCH] SSL support for the mail proxy module

and regards, FDS. 2014-09-14 1:14 GMT+02:00 Kunal Pariani kpari...@zimbra.com: # HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1410649455 18000 # Sat Sep 13 18:04:15 2014 -0500 # Node ID 5c2524403ab7c870b1fa7294f935d3292f25fd1d # Parent

Re: [PATCH] SSL support for the mail proxy module

for the mail proxy module Hello! On Mon, Sep 08, 2014 at 10:19:17AM -0700, Quanah Gibson-Mount wrote: --On Friday, August 22, 2014 5:13 PM -0500 Kunal Pariani kpari...@zimbra.com wrote: Any comments on this yet ? Any nginx developers who could comment on this? Some obvious problems

[PATCH] The directives such as user, rlimit_core should also be effective on master process

# HG changeset patch # User Kunal Pariani kpari...@zimbra.com # Date 1407194790 25200 # Mon Aug 04 16:26:30 2014 -0700 # Node ID f25ab24517bb5e45b1b7fa1a1502b907f2cff213 # Parent f8764e20fcd7f87d98fe97f82b2a8d0a77ed9097 The directives such as user, rlimit_core should also be effective

Re: proxy_pass to different upstreams based on a cookie in the http request header

Thanks for your answer. Worked great for me.. On Wed, Jun 11, 2014 at 10:10 AM, Francis Daly fran...@daoine.org wrote: On Wed, Jun 11, 2014 at 12:46:41AM -0700, Kunal Pariani wrote: Hi there, Am wondering if there is a way to proxy (i.e proxy_pass inside location directive) to different

proxy_pass to different upstreams based on a cookie in the http request header

Hello, Am wondering if there is a way to proxy (i.e proxy_pass inside location directive) to different set of upstreams based on whether a particular cookie is present or not in a http request header. Thanks -Kunal ___ nginx mailing list nginx@nginx.org

Re: debug logs not getting generated

Never mind. Got it working. Had a script which was overwriting the loglevel value in the conf file after restarting nginx. Thanks for the help. On Sat, Mar 29, 2014 at 3:36 PM, Kunal Pariani kunalv...@gmail.com wrote: 3) Make sure you've restarted nginx (or upgraded running binary). 4) Make

Re: debug logs not getting generated

:04PM -0700, Kunal Pariani wrote: Hello, I followed this http://nginx.org/en/docs/debugging_log.html. Have nginx built with --with-debug and set the the error_log in the following 2 files (nginx.conf.main inside http { } in nginx.conf.web). But still i don't see debug level logging getting

debug logs not getting generated

Hello, I followed this http://nginx.org/en/docs/debugging_log.html. Have nginx built with --with-debug and set the the error_log in the following 2 files (nginx.conf.main inside http { } in nginx.conf.web). But still i don't see debug level logging getting generated in the files specified.

Re: Build nginx on Mac OS X mavericks

://twitter.com/kworthington On Thu, Mar 27, 2014 at 7:17 AM, Maxim Dounin mdou...@mdounin.ru wrote: Hello! On Wed, Mar 26, 2014 at 06:33:56PM -0700, Kunal Pariani wrote: Hello, Has anyone tried building nginx code on Mac ? I get the following error while building. Have installed pcre and other

Build nginx on Mac OS X mavericks

Hello, Has anyone tried building nginx code on Mac ? I get the following error while building. Have installed pcre and other needed libraries *src/mail/ngx_mail_handler.c:1152:30: **error: **use of undeclared identifier 'sasl_callback_ft'; did you mean* * 'sasl_callback_t'?*

Re: nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

I used the web browser but didn't see this Content-disposition header in the response. Only saw these response headers. 1. Response Headersview source 1. Connection: keep-alive 2. Content-Length: 1159 3. Content-Type: text/html 4. Date: Mon, 24

Re: nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

hmm..thanks Lukas. So its my backend server only which is causing this issue. Thanks -Kunal On Mon, Mar 24, 2014 at 12:43 PM, Lukas Tribus luky...@hotmail.com wrote: FYI, nginx has not problems passing filenames with spaces along: # curl -I

Re: nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

Never mind there's nothing wrong with nginx here. It was one of the response headers sent by an upstream server (mainly Content-Description: 2013923 10H56M56S633_PV.doc�) including this non-ascii char '?' which the nginx didn't like and hence flagged it saying that it received an invalid header.

nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

Hello, I have nginx set as a reverse proxy for a mail server and it throws this 502 (invalid header) error while trying to fetch a file with a space in the filename. Any clues on where is this bug in the nginx code ? I searched on the net and found this one forum but it points to some issue in the

Re: nginx throws a 502 (invalid header) when downloading a file attachment if filename has a space character

What debugs should i enable how to see these response headers ? I do see this error though. 2014/03/03 14:04:32 [error] 11259#0: *6 upstream sent invalid header while reading response header from upstream, client: 127.0.0.1, server: xxx.default, request: GET