[PATCH 1 of 4] Contrib: vim syntax, allow multiline config by skipempty

2017-03-03 Thread othree
# HG changeset patch # User othree # Date 1488526499 -28800 # Fri Mar 03 15:34:59 2017 +0800 # Node ID d91e05e761d148d7299017b62d581c6a1429bbd4 # Parent a72886067bbbfe854617976839434df76f0565b6 Contrib: vim syntax, allow multiline config by skipempty. diff --git a/contrib/vim/syntax/nginx.v

[PATCH 3 of 4] Contrib: vim syntax, highlight HTTP status code

2017-03-03 Thread othree
# HG changeset patch # User othree # Date 1488526564 -28800 # Fri Mar 03 15:36:04 2017 +0800 # Node ID b88ed85b7b4f3ea5a586f4f58251481348c502f1 # Parent 47796d6e4c8af080e515fa45699cf23cd10cf7ad Contrib: vim syntax, highlight HTTP status code. diff --git a/contrib/vim/syntax/nginx.vim b/cont

[PATCH 2 of 4] Contrib: vim syntax, highlight rewrite flag

2017-03-03 Thread othree
# HG changeset patch # User othree # Date 1488526542 -28800 # Fri Mar 03 15:35:42 2017 +0800 # Node ID 47796d6e4c8af080e515fa45699cf23cd10cf7ad # Parent d91e05e761d148d7299017b62d581c6a1429bbd4 Contrib: vim syntax, highlight rewrite flag. diff --git a/contrib/vim/syntax/nginx.vim b/contrib/

[PATCH 4 of 4] Contrib: vim syntax, remove unecessary ngxBlock

2017-03-03 Thread othree
# HG changeset patch # User othree # Date 1488538568 -28800 # Fri Mar 03 18:56:08 2017 +0800 # Node ID 433844daf574dbf89390e574201b3db417337cdd # Parent b88ed85b7b4f3ea5a586f4f58251481348c502f1 Contrib: vim syntax, remove unecessary ngxBlock. ngxBlock breaks highlighting for the following c

RE: New ssl var: $ssl_client_ms_upn

2017-03-03 Thread Dave Bevan
Hi. At the risk of being shot down in flames, what else do I need to do to comply with your requirements to get my patch accepted such that it appears at http://hg.nginx.org/nginx/ ? I'm happy to contribute documentation, add a test case to the nginx-test repo etc. Many thanks, -- Dave Bevan

Re: New ssl var: $ssl_client_ms_upn

2017-03-03 Thread Maxim Dounin
Hello! On Fri, Mar 03, 2017 at 12:08:56PM +, Dave Bevan wrote: > At the risk of being shot down in flames, what else do I need to > do to comply with your requirements to get my patch accepted > such that it appears at http://hg.nginx.org/nginx/ ? You were already told that: - There are o

Re: [PATCH 4 of 4] Contrib: vim syntax, remove unecessary ngxBlock

2017-03-03 Thread Maxim Dounin
Hello! On Fri, Mar 03, 2017 at 06:56:59PM +0800, othree wrote: > # HG changeset patch > # User othree > # Date 1488538568 -28800 > # Fri Mar 03 18:56:08 2017 +0800 > # Node ID 433844daf574dbf89390e574201b3db417337cdd > # Parent b88ed85b7b4f3ea5a586f4f58251481348c502f1 > Contrib: vim syntax

Re: [PATCH 4 of 4] Contrib: vim syntax, remove unecessary ngxBlock

2017-03-03 Thread OOO
Hi I made a sample and take screenshot[1]. This one (remove current ngxBlock) is a blocker for some other changes. [1]:https://www.flickr.com/photos/othree/32843758310/ And about the *ngxBlock* you talked about in the last paragraph. I think you are talking about curly bracket block: http {

module init order & embedded variables

2017-03-03 Thread Pillai, Saju
My module needs to access variables created by the ngx_http_ssl_module. Iam trying to find the index of these variables from my module_init, but I am finding this to be sensitive to the order in which the modules are compiled into the nginx binary. My plan was to locate the indices for the varia

Re: [PATCH 4 of 4] Contrib: vim syntax, remove unecessary ngxBlock

2017-03-03 Thread Maxim Dounin
Hello! On Fri, Mar 03, 2017 at 11:37:36PM +0800, OOO wrote: > I made a sample and take screenshot[1]. > This one (remove current ngxBlock) is a blocker for some other changes. > > [1]:https://www.flickr.com/photos/othree/32843758310/ Ah, ok, I see. The problem only happens if there is an inde

Re: [PATCH] Resolver: parse hosts file entries

2017-03-03 Thread Thibault Charbonnier
Hi, Just curious what is the community's stance on this? If the feature is desired but the patch isn't good, I am willing to receive feedback and improve it. If not desired, may I be so curious as to ask why? I hope the ping is considered ok. Best, Thibault __