[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1690211081 -10800 # Mon Jul 24 18:04:41 2023 +0300 # Node ID 904c99bede1770d92566b56939c5b6ec85f05b55 # Parent c209dc4eed1737261c97a044d23f5fb9afbd9d45 Contrib: vim syntax, update core and 3rd party module directives. List of 3rd party

Re: [PATCH] Contrib: vim syntax, update core and 3rd party module directives.

On 20.07.2023 19:32, Maxim Dounin wrote: > (Also, it might be a good idea to keep directives introduced by > commercial extensions separately.) In addition to ngxDirectiveBlock and ngxDirective I should introduce ngxDirectiveBlockCommercial and ngxDirectiveCommercial and [allow users to] use

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1689803114 -10800 # Thu Jul 20 00:45:14 2023 +0300 # Node ID dee0e911380d18773dad06d45b845a124474f12a # Parent c209dc4eed1737261c97a044d23f5fb9afbd9d45 Contrib: vim syntax, update core and 3rd party module directives. List of 3rd party

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 166880 -10800 # Sat Jun 18 15:54:40 2022 +0300 # Node ID 81096862f8f13438ca059779cbc2097db8c0ad68 # Parent 861f076eab72dab85bd5eaa56da770f8b10aa8ad Contrib: vim syntax, update core and 3rd party module directives. List of 3rd party

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1640023368 -7200 # Mon Dec 20 20:02:48 2021 +0200 # Node ID 4719937b5dcbc5345e1a4cbf4bf84d2da4e316f8 # Parent a7a77549265ef46f1f0fdb3897f4beabf9e09c40 Contrib: vim syntax, update core and 3rd party module directives. diff -r a7a77549265e -r

Re: [PATCH] Variable $time_short.

On 29.05.2021 0:55, Maxim Dounin wrote: Main purpose of variable $time_short is usage for logging, access.log. Existing variables $time_iso8601 and $time_local has bad readability, because these variables contains timezone after seconds and it has no space between date and time fields.

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1622366760 -10800 # Sun May 30 12:26:00 2021 +0300 # Node ID e3c137f6caa6c6b979e8eb8647d00a293fe1f112 # Parent f5de03f308a6d7864b7d5108a968db56585b9a9b Contrib: vim syntax, update core and 3rd party module directives. diff -r f5de03f308a6

Re: [PATCH] Variable $time_short.

On 27.05.2021 20:25, Maxim Dounin wrote: Variable $time_short. Variable $time_short in form "1970/09/28 12:00:00". Added to ngx_http_core_module, ngx_http_log_module, and ngx_stream_core_module. You may want to be more specific about expected use cases, and why existing time variables are

[PATCH] Variable $time_short.

# HG changeset patch # User Gena Makhomed # Date 1622061379 -10800 # Wed May 26 23:36:19 2021 +0300 # Node ID b3c942ec8a13bc8f6cd4b3e2385acb8c14502c0d # Parent f5de03f308a6d7864b7d5108a968db56585b9a9b Variable $time_short. Variable $time_short in form "1970/09/28 12:00:00&qu

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1609240437 -7200 # Tue Dec 29 13:13:57 2020 +0200 # Node ID ed5770c4a49f969949a9b7480af6f75d3aa2eaa0 # Parent 82228f955153527fba12211f52bf102c90f38dfb Contrib: vim syntax, update core and 3rd party module directives. diff -r 82228f955153 -r

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1590509831 -10800 # Tue May 26 19:17:11 2020 +0300 # Node ID f40470c7b2e00cca839c5f0ec15a404705f7ea0e # Parent 02f2f129abc013707b184cf4bb9ac2d07760be27 Contrib: vim syntax, update core and 3rd party module directives. diff -r 02f2f129abc0

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1561880341 -10800 # Sun Jun 30 10:39:01 2019 +0300 # Node ID f298b850ea1a8499b3ea51bde571d010dc7dfc69 # Parent 35ea9229c71a9207a24e51f327e1749e3accb26c Contrib: vim syntax, update core and 3rd party module directives. diff -r 35ea9229c71a

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed # Date 1545661810 -7200 # Mon Dec 24 16:30:10 2018 +0200 # Node ID 19f1cbe0be527cbbfea8d8e7e8693352e72e745b # Parent 294162223c7c51a147c07eba36d0506d54edbf20 Contrib: vim syntax, update core and 3rd party module directives. diff -r 294162223c7c -r

Re: [PATCH] Cache: status must be less then 599 in *_cache_valid directives.

On 24.09.2018 21:00, Maxim Dounin wrote: # HG changeset patch # User Gena Makhomed # Date 1537810006 -10800 # Mon Sep 24 20:26:46 2018 +0300 # Node ID fc6c7e03edaad907d6a85afab009cb5c1fa43c56 # Parent 17092295247709a533acca09f990c13337a24948 Cache: status must be less then 599

[PATCH] Cache: status must be less then 599 in *_cache_valid directives.

des? # HG changeset patch # User Gena Makhomed # Date 1537810006 -10800 # Mon Sep 24 20:26:46 2018 +0300 # Node ID fc6c7e03edaad907d6a85afab009cb5c1fa43c56 # Parent 17092295247709a533acca09f990c13337a24948 Cache: status must be less then 599 in *_cache_valid directives. Previously, configurations

[PATCH] Add 307 and 308 to default response codes for xxxxx_cache_valid.

cing these shortcuts, as they looks rather dangerous for the unwary. Ok, thank you for detailed explanation. What about adding 307 and 308 to list of default response codes? # HG changeset patch # User Gena Makhomed # Date 1537543090 -10800 # Fri Sep 21 18:18:10

[PATCH] Allow 1xx 2xx 3xx 4xx 5xx codes in xxxxx_cache_valid directives.

# HG changeset patch # User Gena Makhomed # Date 1537528104 -10800 # Fri Sep 21 14:08:24 2018 +0300 # Node ID a7533f3f3138fe5524a0f14293da4149e65b1402 # Parent 87d2ea860f380dc8418c97c0163412f53c2d008e Allow 1xx 2xx 3xx 4xx 5xx codes in x_cache_valid directives. For example, config

Re: RSS

On 09.07.2018 11:39, Valentin V. Bartenev wrote: bot mitigation mechanism written as custom "C" module or written using only njs, without 3rd party modules? It's pretty easy to write one using only njs. Can you make reference implementation open source under permissive software license?

Re: RSS

On 09.07.2018 10:41, Sergey Budnevitch wrote: atom-tags, atom-log, archive were removed from bot mitigation mechanism One more bug: If you try to open some page from RSS, for example: http://hg.nginx.org/nginx/rev/54683f650cbd you will see only plain html, this is not expected. Firefox

Re: RSS

On 09.07.2018 10:41, Sergey Budnevitch wrote: https://hg.nginx.org/nginx/atom-log https://hg.nginx.org/pkg-oss/atom-log https://hg.nginx.org/nginx.org/atom-log stop working, instead of RSS feed html+javascript returned. RSSOwl can't execute javascript and don't see these RSS feeds. Also I

RSS

Hello, All! RSS https://hg.nginx.org/nginx/atom-log https://hg.nginx.org/pkg-oss/atom-log https://hg.nginx.org/nginx.org/atom-log stop working, instead of RSS feed html+javascript returned. RSSOwl can't execute javascript and don't see these RSS feeds. Also I can't download

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1523382230 -10800 # Tue Apr 10 20:43:50 2018 +0300 # Node ID 4049f2a9bc4e8de556f659769ea061f5b1b244e1 # Parent 1ad1cdfe7409db7feec0d9c4f715d46175da1ca5 Contrib: vim syntax, update core and 3rd party module directives.

Re: [PATCH] Contrib: vim syntax, update core and 3rd party module directives.

On 10.04.2018 20:47, Gena Makhomed wrote: # HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1523382230 -10800 #  Tue Apr 10 20:43:50 2018 +0300 # Node ID 4049f2a9bc4e8de556f659769ea061f5b1b244e1 # Parent  1ad1cdfe7409db7feec0d9c4f715d46175da1ca5 Contrib: vim syntax,

Re: nginx documentation

On 11.04.2018 15:56, Yaroslav Zhuravlev wrote: Directive limit_zone still exists in nginx documentation, but this directive was removed from nginx in version 1.7.6, long time ago. This is the only one directive, which is removed from nginx, but still exists in nginx documentation on site

nginx documentation

On 10.04.2018 19:23, Ruslan Ermilov wrote: +syn keyword ngxDirectiveDeprecated contained status +syn keyword ngxDirectiveDeprecated contained status_format +syn keyword ngxDirectiveDeprecated contained status_zone The status_zone directive is not deprecated despite the fact that it's

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1523382230 -10800 # Tue Apr 10 20:43:50 2018 +0300 # Node ID 4049f2a9bc4e8de556f659769ea061f5b1b244e1 # Parent 1ad1cdfe7409db7feec0d9c4f715d46175da1ca5 Contrib: vim syntax, update core and 3rd party module directives.

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1523373890 -10800 # Tue Apr 10 18:24:50 2018 +0300 # Node ID 739582ed66b790646c463b3abe5f51a94043cd41 # Parent 1ad1cdfe7409db7feec0d9c4f715d46175da1ca5 Contrib: vim syntax, update core and 3rd party module directives.

Re: [PATCH] Contrib: remove obsoleted script geo2nginx.pl.

On 05.04.2018 10:53, Gena Makhomed wrote: # HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1522914140 -10800 #  Thu Apr 05 10:42:20 2018 +0300 # Node ID 4f14c557c910f88960dbccf6bd3268eb69b31029 # Parent  d4cc2edb4ff8391d0c7419e91e6fcc988c510654 Contrib: remove obs

[PATCH] Contrib: vim syntax, update 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1522914365 -10800 # Thu Apr 05 10:46:05 2018 +0300 # Node ID 463bb400efc9d3d6f3b5b314eedf2321e379e4dd # Parent 4f14c557c910f88960dbccf6bd3268eb69b31029 Contrib: vim syntax, update 3rd party module directives. d

[PATCH] Contrib: remove obsoleted script geo2nginx.pl.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1522914140 -10800 # Thu Apr 05 10:42:20 2018 +0300 # Node ID 4f14c557c910f88960dbccf6bd3268eb69b31029 # Parent d4cc2edb4ff8391d0c7419e91e6fcc988c510654 Contrib: remove obsoleted script geo2nginx.pl. GeoLite Legacy Dat

Re: nginx undocumented directives

On 13.02.2018 13:02, Yaroslav Zhuravlev wrote: Documentation added for smtp_client_buffer and smtp_greeting_delay Ok, thank you. But directive subrequest_output_buffer_size is still undocumented. It is added by http://hg.nginx.org/nginx/rev/20f139e9ffa8#l4.7 It is undocumented by mistake

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1521364274 -7200 # Sun Mar 18 11:11:14 2018 +0200 # Node ID 169d0eb76de7ffe2b2ea3005e4268542b5fc31a5 # Parent c2a0a838c40f791efc08567c791e58c894aa5c17 Contrib: vim syntax, update core and 3rd party module directives. d

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1519907674 -7200 # Thu Mar 01 14:34:34 2018 +0200 # Node ID 42536cf64a89641b90bc0db7223fe60703d663e0 # Parent 20f139e9ffa84f1a1db6039547cd35fc4534 Contrib: vim syntax, update core and 3rd party module directives. d

[PATCH] Contrib: vim syntax, update core and 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1519907674 -7200 # Thu Mar 01 14:34:34 2018 +0200 # Node ID 42536cf64a89641b90bc0db7223fe60703d663e0 # Parent 20f139e9ffa84f1a1db6039547cd35fc4534 Contrib: vim syntax, update core and 3rd party module directives. d

Re: nginx undocumented directives

On 28.12.2017 15:17, Maxim Dounin wrote: smtp_client_buffer smtp_greeting_delay There are no notes of why these aren't documented. I guess the reason is that mail documentation is mostly contributed, and was never seriously considered by the documentation project. The smtp_client_buffer

[PATCH 2 of 2] Contrib: vim syntax, update 3rd party module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1517476514 -7200 # Thu Feb 01 11:15:14 2018 +0200 # Node ID 2e0de79805eee669cca7e2455010689a3191f268 # Parent 6db472f8dc8ec04754a42ba22e9663cb7e91f2ab Contrib: vim syntax, update 3rd party module directives. A

[PATCH 1 of 2] Contrib: vim syntax, update core module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1517476175 -7200 # Thu Feb 01 11:09:35 2018 +0200 # Node ID 6db472f8dc8ec04754a42ba22e9663cb7e91f2ab # Parent 0b72d545f098b407351a1972fba5d29f2e904507 Contrib: vim syntax, update core module directives. "matc

Re: [PATCH] Upstream: fastcgi_cache_convert_head directive.

On 23.01.2018 14:32, Maxim Dounin wrote: # HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1516650013 -7200 # Mon Jan 22 21:40:13 2018 +0200 # Node ID 4f635c5c8da929eb1e25bc8fbce7d7d5726468cf # Parent cbf59d483c9cd94dc0fb05f1978601d02af69c20 Up

[PATCH] Upstream: fastcgi_cache_convert_head directive.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1516650013 -7200 # Mon Jan 22 21:40:13 2018 +0200 # Node ID 4f635c5c8da929eb1e25bc8fbce7d7d5726468cf # Parent cbf59d483c9cd94dc0fb05f1978601d02af69c20 Upstream: fastcgi_cache_convert_head directive. The directive t

nginx undocumented directives

Hello, All! Scanning nginx sources and nginx documentation I found some directives, which present in nginx sources but absent in nginx documentation: acceptex_read degradation degrade devpoll_changes devpoll_events epoll_events eventport_events gzip_hash gzip_no_buffer gzip_window

[PATCH 2 of 2] Contrib: vim syntax, update core module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1514455265 -7200 # Thu Dec 28 12:01:05 2017 +0200 # Node ID 16674bef9168f70962cafb451a0dd212b37d9c61 # Parent 215684d20d906135281b2540149d354b6e4bb852 Contrib: vim syntax, update core module directives. Removed non-ex

[PATCH] Contrib: vim syntax, listen options.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1514219401 -7200 # Mon Dec 25 18:30:01 2017 +0200 # Node ID c0ce67821e8d151fa98dc6934a80fb962bbdbc4a # Parent 5b9ed8c6f2dcadcdeb0fe9d64e18ac194b881e14 Contrib: vim syntax, listen options. diff -r 5b9ed8c6f2dc -r c0ce67

[PATCH] Contrib: vim syntax, update core module directives.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1514217421 -7200 # Mon Dec 25 17:57:01 2017 +0200 # Node ID 5b9ed8c6f2dcadcdeb0fe9d64e18ac194b881e14 # Parent d91a8c4ac6bb10bb30c598a4f2c993fc34bf8cec Contrib: vim syntax, update core module directives. diff -r d91a8c

Re: [PATCH] Workaround for systemd error messages about nginx pid file.

On 29.11.2017 14:30, Maxim Dounin wrote: No, thanks. As a systemd-specific workaround this definitely should be in the service unit file instead, if at all. Moreover, as previously explained, the message in question is harmless and the workaround is not needed for anything but silencing the

[PATCH] Workaround for systemd error messages about nginx pid file.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1511951401 -7200 # Wed Nov 29 12:30:01 2017 +0200 # Node ID b529ea784244e13d8a5e58a12c8b639351652057 # Parent fc0d06224edac2c7cfbfd9a4def478f285d9957b Workaround for systemd error messages about nginx pid file.

Re: Workaround of race condition between systemd and nginx.

On 30.12.2015 16:51, Jim Popovitch wrote: # HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1451482795 18000 # Wed Dec 30 08:39:55 2015 -0500 # Node ID a340d271b3ffa51c0396a5afc5270cb02b701204 # Parent 1073d7e4e430ddb53b603d151e1a403d10aa420b Workaround of race con

Re: Workaround of race condition between systemd and nginx.

uot; $ curl -s http://nginx.org/en/CHANGES | grep "Gena Makhomed" -- Best regards, Gena ___ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel

Re: Workaround of race condition between systemd and nginx.

On 30.12.2015 20:28, Daniel K. wrote: nginx now requires configured and up network, before starting daemon. Replace network.target with network-online.target is easy workaround. Actually it does not require that at all. nginx failed to start if network is down via systemd race condition.

Re: Workaround of race condition between systemd and nginx.

On 30.12.2015 19:59, Jim Popovitch wrote: BTW, you can read about how openvpn handled this very issue https://community.openvpn.net/openvpn/ticket/462 You can provide patch with solution? I see no need for a patch, and I already explained why nginx failed to start with correct config.

Re: Workaround of race condition between systemd and nginx.

On 30.12.2015 22:40, Daniel K. wrote: nginx failed to start if network is down via systemd race condition. Again, no, nginx failed to start due to a local misconfiguration. Configuration is correct. "nginx -t" syntax check say: nginx: the configuration file /etc/nginx/nginx.conf syntax

Workaround of race condition between systemd and nginx.

# HG changeset patch # User Gena Makhomed <g...@csdoc.com> # Date 1451482795 18000 # Wed Dec 30 08:39:55 2015 -0500 # Node ID a340d271b3ffa51c0396a5afc5270cb02b701204 # Parent 1073d7e4e430ddb53b603d151e1a403d10aa420b Workaround of race condition between systemd and nginx. Just r

Re: How does Nginx look-up cached resource?

On 08.09.2015 4:41, Maxim Dounin wrote: > On the other hand, it might be possible to simplify requirements > of the attack by forcing some authenticated user to load data > under a given key and then retrieve this key contents using a > choosen prefix collision previously calculated. Yes,

Re: How does Nginx look-up cached resource?

On 08.09.2015 3:29, Sergey Brester wrote: There is no obscurity here. Value of proxy_cache_key is known, hash function is known, nginx sources is open and available. If value of proxy_cache_key is known and attackers can generate it, what do you want to protect with some hash value? I want

Re: How does Nginx look-up cached resource?

On 06.09.2015 4:56, Maxim Dounin wrote: The security of the MD5 hash function is severely compromised. A collision attack exists that can find collisions within seconds on a computer with a 2.6 GHz Pentium 4 processor (complexity of 2**24.1) - https://en.wikipedia.org/wiki/MD5#Security I said

Re: How does Nginx look-up cached resource?

On 08.09.2015 0:22, Sergey Brester wrote: Using MurmurHash is not good idea, because attacker can easy make collisions and invalidate popular entries from cache, and this technology can be used for DDoS attacks. (even in case if only one site exists on server with nginx cache) Using secure

Re: How does Nginx look-up cached resource?

On 04.09.2015 22:43, Maxim Dounin wrote: For sure this is something that can be done. The question remains though: how often collisions are observed in practice, is it make sense to do anything additional to protect from collisions and spend resources on it? Even considering only md5, without

Re: [PATCH] Workaround for configuration file test failed under OpenVZ

On 03.08.2015 12:26, Maxim Dounin wrote: Here is the patch with slightly updated commit log and a comment added to the code. Please take a look if it looks fine to you. Yes, updated version of patch is more clean and easy to understand, thank you! # HG changeset patch # User Gena Makhomed

[PATCH] Workaround for configuration file test failed under OpenVZ

# HG changeset patch # User Gena Makhomed g...@csdoc.com # Date 1437674403 14400 # Thu Jul 23 14:00:03 2015 -0400 # Node ID 57ac65580b5bba0cb4bb61dca9d63daec0ceb14c # Parent 341e4303d25be159d4773b819d0ec055ba711afb Workaround for configuration file test failed under OpenVZ. nginx