Re: Is ngx_quic_select_socket_by_dcid good when len < 20 ?

09.03.2021 10:13, Gao,Yan(ACG VCP) пишет: ngx_quic_select_socket_by_dcid     advance_data(sizeof(struct udphdr)); /* skip UDP header */     advance_data(1); /* QUIC flags */     if (data[0] & NGX_QUIC_PKT_LONG) {     advance_data(4); /* skip QUIC version */     len = data[0];  

Re: QUIC: quic retry log error when ngx_exiting

Hi Gao Yan, > On Wed, Mar 03, 2021 at 11:53:57AM +, Gao,Yan(ACG VCP) wrote: > 2021/03/03 19:34:49 [debug] 176572#0: *19974 recvmsg: 111.206.214.32:59242 > fd:12 n:1350 > 2021/03/03 19:34:49 [debug] 176572#0: *19974 quic run > 2021/03/03 19:34:49 [debug] 176572#0: *19974 quic packet rx long

Re: Seeking example of module using theadpool

On Mon, Mar 01, 2021 at 04:07:47AM -0500, dvhh wrote: > Hello, > > I have developed a module which perform long running calculations to produce > the output, unfortunately blocking the server thread from handling other > requests. I am looking at using threadpool, unfortunately there is no >

Re: [PATCH] Add io_uring support in AIO(async io) module

On Tue, Jan 19, 2021 at 03:32:30AM +, Zhao, Ping wrote: > It depends on if disk io is the performance hot spot or not. If yes, > io_uring shows improvement than libaio. With 4KB/100KB length 1 Nginx > thread it's hard to see performance difference because iostat is only > around ~10MB/100MB

Re: [PATCH] Add io_uring support in AIO(async io) module

inal Message- From: nginx-devel On Behalf Of Vladimir Homutov Sent: Monday, January 18, 2021 3:28 PM To: nginx-devel@nginx.org Subject: Re: [PATCH] Add io_uring support in AIO(async io) module On Thu, Jan 14, 2021 at 05:53:17AM +, Zhao, Ping wrote: # HG changeset patch # User Ping Zhao #

Re: [PATCH] Add io_uring support in AIO(async io) module

On Thu, Jan 14, 2021 at 05:53:17AM +, Zhao, Ping wrote: > # HG changeset patch > # User Ping Zhao > # Date 1610554205 18000 > # Wed Jan 13 11:10:05 2021 -0500 > # Node ID 95886c3353dc80a3da215027c1e0f2141e47e911 > # Parent b055bb6ef87e49232a7fcb4e5334b8efda3b6499 > Add io_uring support

Re: [PATCH] Use io_uring for async io access

On Mon, Jan 11, 2021 at 07:05:28AM +, Zhao, Ping wrote: > Hello Nginx Developers, > > This is a patch of Nginx io_uring for async io access. Would like to receive > your comments. > > Thanks, > Ping Hi Zhao Ping, Unfortunately I was not able to apply the patch properly, it shows a lot of

Re: accept4() support SOCK_CLOEXEC flag

16.12.2020 09:41, 张翔 пишет: # HG changeset patch # User Zhang Xiang > # Date 1608099124 -28800 #      Wed Dec 16 14:12:04 2020 +0800 # Node ID a685d9c04acdb4ec71fd9f176415917c217af630 # Parent  82228f955153527fba12211f52bf102c90f38dfb Mail: accept4() support

Re: [NGINX] accept4() support SOCK_CLOEXEC flag

16.12.2020 10:05, 张翔 пишет: # HG changeset patch # User Zhang Xiang > # Date 1608099124 -28800 #      Wed Dec 16 14:12:04 2020 +0800 # Node ID a685d9c04acdb4ec71fd9f176415917c217af630 # Parent  82228f955153527fba12211f52bf102c90f38dfb Event: accept4() support

Re: [PATCH 8 of 8] new io_uring event module

First, thank you for sharing the patchset! We are always looking at new features that appear in kernels and may be useful in nginx. There are a lof of shiny features, but it is a long way for them to mature and be adopted in nginx. Currently we are not considering adding such functionality. The

[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/908f48bd3c2f branches: changeset: 7735:908f48bd3c2f user: Vladimir Homutov date: Thu Nov 05 22:37:27 2020 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

[nginx] Core: added format specifiers to output binary data as hex.

details: https://hg.nginx.org/nginx/rev/a46fcf101cfc branches: changeset: 7736:a46fcf101cfc user: Vladimir Homutov date: Wed Oct 28 10:56:11 2020 +0300 description: Core: added format specifiers to output binary data as hex. Now "s", "V", and "v" for

Re: [PATCH] Use BPF to distribute packet to different work thread.

On Thu, Sep 10, 2020 at 05:22:12AM +, Liu, Qiao wrote: > # HG changeset patch > # User Liu Qiao > # Date 1599735293 14400 > # Thu Sep 10 06:54:53 2020 -0400 > # Node ID f79d524a2cc0093c53490f947564e42371cf944f > # Parent da5e3f5b16733167142b599b6af3ce9469a07d52 > Use BPF to distribute

Re: [PATCH] Stream: added extra variables for logging

, 2020 at 10:54 AM Vladimir Homutov wrote: On Fri, Jul 10, 2020 at 06:10:44PM +0200, Hinel Balázs wrote: Hi, The first one (upstream_addr) contains the address and port in one single variable, but we need to put them separately into the access log, that's why we need the two variables. The second one

Re: [PATCH] Stream: added extra variables for logging

resses are separated by commas, e.g. “192.168.1.1:12345, 192.168.1.2:12345, unix:/tmp/sock”. If a server cannot be selected, the variable keeps the name of the server group. > > > On Fri, Jul 10, 2020 at 4:03 PM Vladimir Homutov wrote: > > > > On Thu, Jul 09, 2020 at 04:2

Re: Nginx not retrying failed UDP message

On Thu, Jul 09, 2020 at 02:42:52PM -0400, harsh wrote: > Hi, > > We are using NGINX as Load Balancer for load balancing RADIUS UDP traffic. > > It seems NGINX is not retrying to send messages to another upstream server > if one of the upstream servers is down. > > We are using NGINX 1.16.1. But

Re: [PATCH] Stream: added extra variables for logging

On Thu, Jul 09, 2020 at 04:20:16PM +0200, Balazs Hinel wrote: > # HG changeset patch > # User Balazs Hinel > # Date 1594225255 -7200 > # Wed Jul 08 18:20:55 2020 +0200 > # Node ID ab1359d9762109d1cccb06fbe85e17168b51ebed > # Parent 2ab0ecfe5a5f02f7214b02c8a1f9d6c5843d310e > Stream: added

Re: nginx-ldap-auth

15.04.2020 03:30, de...@webmaster.spb.ru пишет: Добрый день Есть в амазоне кластер, с приватной сетью, вход через OpenVPN, после входа у всех один внутренний айпи. Используем nginx-ldap-auth, но у меня получилось завести его в 2 режимах: 1) авторизуется 1 человек, и все кто через впн могут

[nginx] Made ngx_http_get_forwarded_addr_internal() non-recursive.

details: https://hg.nginx.org/nginx/rev/1055e43e4fab branches: changeset: 7624:1055e43e4fab user: Vladimir Homutov date: Tue Feb 11 13:22:44 2020 +0300 description: Made ngx_http_get_forwarded_addr_internal() non-recursive. diffstat: src/http/ngx_http_core_module.c | 62

[nginx] gRPC: variables support in the "grpc_pass" directive.

details: https://hg.nginx.org/nginx/rev/6439ef81e37d branches: changeset: 7619:6439ef81e37d user: Vladimir Homutov date: Fri Jan 17 12:13:02 2020 +0300 description: gRPC: variables support in the "grpc_pass" directive. diffstat: src/http/modules/ngx_http_grpc_modul

Re: [PATCH nginx v2] remove ngx_cpuinfo, use sysconf or define

On Thu, Jan 16, 2020 at 07:39:07AM -0800, Joe Konno wrote: > Scroll to bottom: > > On 1/16/20 6:43 AM, Vladimir Homutov wrote: > > On Fri, Jan 03, 2020 at 02:39:29PM -0800, Joe Konno wrote: > >> # HG changeset patch > >> # User Joe Konno > >> # Date 157

Re: [PATCH nginx v2] remove ngx_cpuinfo, use sysconf or define

On Fri, Jan 03, 2020 at 02:39:29PM -0800, Joe Konno wrote: > # HG changeset patch > # User Joe Konno > # Date 1578075036 28800 > # Fri Jan 03 10:10:36 2020 -0800 > # Node ID b66ee34cea2f539bb8ce4986d6bd332f75ee06b6 > # Parent f1720934c45be1c6469841a55d1f31fe9a630c85 > remove ngx_cpuinfo,

[nginx] Core: removed dead code in ngx_rbtree_delete().

details: https://hg.nginx.org/nginx/rev/7fdcf308e0f0 branches: changeset: 7576:7fdcf308e0f0 user: Vladimir Homutov date: Mon Sep 30 16:39:20 2019 +0300 description: Core: removed dead code in ngx_rbtree_delete(). The result of ngx_rbtree_min() is always a node with the left child

[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/d34a81b49214 branches: changeset: 7575:d34a81b49214 user: Vladimir Homutov date: Mon Sep 30 16:43:16 2019 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

Re: How is the progress to support DTLS

On Tue, Sep 10, 2019 at 05:12:48AM -0400, everhardt wrote: > I have been using it for more than a year now for more than 500 IoT devices > with a cellular connection that connect on average about 4 times per day. My > experience has been very positive: easy to set up and no issues at all (both >

Re: FIPS support in nginx?

On Fri, Jun 14, 2019 at 02:26:49PM -0400, tlemons wrote: > Hi > > Does nginx have a 'FIPS mode'? If so, where can I find this documented? > > Thanks! > tl > nginx uses openSSL library for all cryptographic operations. Thus it is enough to turn on FIPS mode in the library. For example, here [1]

Re: Using round robin for load balancing if hash key is empty

On Wed, May 22, 2019 at 09:59:46PM +0200, Niklas Keller wrote: > Hey, > > I'd like to propose falling back to round robin if the hash key is > empty. This allows using hashed cookie values for sticky sessions > while using round robin for all requests that do not carry any session > information

[nginx] Core: enabled "include" in any context (ticket #1615).

details: https://hg.nginx.org/nginx/rev/b7a7c02aea3a branches: changeset: 7502:b7a7c02aea3a user: Vladimir Homutov date: Tue Apr 09 11:40:20 2019 +0300 description: Core: enabled "include" in any context (ticket #1615). diffstat: src/core/ngx_conf_file.h | 2 +- 1 fil

[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/88fd9f3976f6 branches: changeset: 7501:88fd9f3976f6 user: Vladimir Homutov date: Wed Apr 24 13:41:29 2019 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

[nginx] Version bump.

details: https://hg.nginx.org/nginx/rev/134343f2a877 branches: changeset: 7438:134343f2a877 user: Vladimir Homutov date: Thu Jan 17 14:31:01 2019 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

[nginx] Added the ngx_http_test_required_predicates() function.

details: https://hg.nginx.org/nginx/rev/5efc23d83bc2 branches: changeset: 7439:5efc23d83bc2 user: Vladimir Homutov date: Thu Jan 17 14:31:04 2019 +0300 description: Added the ngx_http_test_required_predicates() function. In contrast to ngx_http_test_predicates(), it requires all

[nginx] Autoindex: fixed possible integer overflow on 32-bit systems.

details: https://hg.nginx.org/nginx/rev/a91b93f3f3e7 branches: changeset: 7435:a91b93f3f3e7 user: Vladimir Homutov date: Tue Dec 25 12:59:24 2018 +0300 description: Autoindex: fixed possible integer overflow on 32-bit systems. diffstat: src/http/modules

Re: Start nginx with all servers weighted=0

On 19.12.2018 22:47, Pablo Fischer wrote: > Hi all, > > Sorry for posting to nginx-devel but looking to see if I'm missing any > details. I'm building a service discovery integration on top of our > Nginx, things work fine but there are two caveats: > > - Nginx does not allow you to start with an

[nginx] Upstream: removed unused ngx_http_upstream_t.timeout field.

details: http://hg.nginx.org/nginx/rev/e8bdd322d7a6 branches: changeset: 7396:e8bdd322d7a6 user: Vladimir Homutov date: Wed Nov 21 13:40:36 2018 +0300 description: Upstream: removed unused ngx_http_upstream_t.timeout field. diffstat: src/http/ngx_http_upstream.h | 2 -- 1 files

[nginx] Stream: session completion check code moved to a separate function.

details: http://hg.nginx.org/nginx/rev/04ff25798002 branches: changeset: 7392:04ff25798002 user: Vladimir Homutov date: Mon Nov 12 12:05:03 2018 +0300 description: Stream: session completion check code moved to a separate function. The code refactored to simplify

[nginx] Stream: proxy_requests directive.

details: http://hg.nginx.org/nginx/rev/4698cede59ff branches: changeset: 7393:4698cede59ff user: Vladimir Homutov date: Mon Nov 12 16:29:30 2018 +0300 description: Stream: proxy_requests directive. The directive allows to drop binding between a client and existing UDP stream

[nginx] Upstream: proxy_socket_keepalive and friends.

details: http://hg.nginx.org/nginx/rev/8b68d50090e4 branches: changeset: 7371:8b68d50090e4 user: Vladimir Homutov date: Wed Oct 03 14:08:51 2018 +0300 description: Upstream: proxy_socket_keepalive and friends. The directives enable the use of the SO_KEEPALIVE option on upstream

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/aa1c9f846567 branches: changeset: 7370:aa1c9f846567 user: Vladimir Homutov date: Wed Oct 03 17:02:44 2018 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diffs (14

Re: Redirect to external site

On Mon, Oct 01, 2018 at 12:22:59PM -0700, Brian W. wrote: > I have gotten the ldap setup working with their backend-sample-app.py file > properly and it displays the hello world message. What I cannot figure out > is how to redirect it to another url on another machine, as opposed to that > local

[nginx] Upstream: fixed request chain traversal (ticket #1618).

details: http://hg.nginx.org/nginx/rev/15ea84e65d07 branches: changeset: 7341:15ea84e65d07 user: Vladimir Homutov date: Fri Aug 24 12:19:37 2018 +0300 description: Upstream: fixed request chain traversal (ticket #1618). The problem does not manifest itself currently, because

Re: “max conns” in upstream is not working what I've expected;

On Tue, Aug 21, 2018 at 10:58:15PM -0400, jinsam.kim wrote: > Hello Super Heroes. > > I want to limit connections in a service. So I used max_conns directive in > upstream. > > But it allows twice connections as many as I've set. > > So, I suspected myself. Maybe… Am I used the direction in wrong

[nginx] Upstream: ngx_http_upstream_random module.

details: http://hg.nginx.org/nginx/rev/f2396ecf608b branches: changeset: 7301:f2396ecf608b user: Vladimir Homutov date: Fri Jun 15 11:46:14 2018 +0300 description: Upstream: ngx_http_upstream_random module. The module implements random load-balancing algorithm with optional second

[nginx] Syslog: install cleanup handler only once.

details: http://hg.nginx.org/nginx/rev/7f9935f07fe9 branches: changeset: 7277:7f9935f07fe9 user: Vladimir Homutov <v...@nginx.com> date: Mon May 14 22:50:57 2018 +0300 description: Syslog: install cleanup handler only once. If a socket was re-opened due to an error (02c235

[nginx] Syslog: re-open syslog udp socket on send error (ticket #1477).

details: http://hg.nginx.org/nginx/rev/fa0e093b64d7 branches: changeset: 7272:fa0e093b64d7 user: Vladimir Homutov <v...@nginx.com> date: Tue May 08 19:35:56 2018 +0300 description: Syslog: re-open syslog udp socket on send error (ticket #1477). Previously, only unix domain s

Re: nginx development guide

13.02.2017 12:38, Vladimir Homutov пишет: > Hello all! > > We are glad to share with first results of our ongoing efforts to create > documentation for nginx developers: the development guide document [1]. > > The guide is not yet 100% complete and more parts to follow. &g

[nginx] Core: fixed build, broken by 63e91f263a49.

details: http://hg.nginx.org/nginx/rev/1fd992589ffe branches: changeset: 7254:1fd992589ffe user: Vladimir Homutov <v...@nginx.com> date: Mon Apr 02 20:38:43 2018 +0300 description: Core: fixed build, broken by 63e91f263a49. Both Solaris and Windows define "s_addr&

Re: Access Nginx variables from HTTP modules

On Thu, Mar 29, 2018 at 04:17:02PM +0100, Paulo Silva wrote: > Hi everyone, > can you point me the right way to access Nginx variables from my HTTP module? > > I am looking for a way to read the $request_id value from within one > of my modules' functions. >

[nginx] Core: style.

details: http://hg.nginx.org/nginx/rev/7bdab16c55f1 branches: changeset: 7252:7bdab16c55f1 user: Vladimir Homutov <v...@nginx.com> date: Tue Mar 27 18:39:38 2018 +0300 description: Core: style. diffstat: src/core/ngx_proxy_protocol.c | 29 ++--- 1

[nginx] Core: added processing of version 2 of the PROXY protocol.

details: http://hg.nginx.org/nginx/rev/416953ef0428 branches: changeset: 7251:416953ef0428 user: Vladimir Homutov <v...@nginx.com> date: Thu Mar 22 15:55:28 2018 +0300 description: Core: added processing of version 2 of the PROXY protocol. The protocol used on inbound conn

Re: Routing based on ALPN

On Sun, Feb 25, 2018 at 08:16:18PM +0100, Wiktor Kwapisiewicz via nginx wrote: > >> Is there a way to access and save ALPN value to a variable? > > > > It should possible to parse the incoming buffer with > > https://nginx.org/r/js_filter and create a variable to make a routing > > decision on.

Re: Nginx Directory Autoindex

On Fri, Mar 02, 2018 at 02:03:36PM +, James wrote: > On 02/03/2018 11:33, Luciano Mannucci wrote: > > >> I'd like the option of order by date, "ls -t", "ls -rt". This helps > >> because the text order of numbers is "10 11 8 9", see: > >> > >> http://nginx.org/download/ > > Well, this is way

[nginx] Access log: support for disabling escaping (ticket #1450).

details: http://hg.nginx.org/nginx/rev/265c29b0b8b8 branches: changeset: 7223:265c29b0b8b8 user: Vladimir Homutov <v...@nginx.com> date: Thu Mar 01 11:42:55 2018 +0300 description: Access log: support for disabling escaping (ticket #1450). Based on patches by Johannes

Re: Nginx Directory Autoindex

On Wed, Feb 28, 2018 at 07:03:22PM +0100, Luciano Mannucci wrote: > > Hello all, > > I have a directory served by nginx via autoindex (That works perfectly > as documented :). I need to show the content in reverse order (ls -r), > is there any rather simple method? > > Thanks in advance, Hello

Re: Antw: [PATCH 1 of 2] Access log: Support for disabling escaping

to avoid this), please take a look. See also ticket 1450: https://trac.nginx.org/nginx/ticket/1450 # HG changeset patch # User Vladimir Homutov <v...@nginx.com> # Date 1519834295 -10800 # Wed Feb 28 19:11:35 2018 +0300 # Node ID d420ce6b46768ea7eb23bdec84f9922122

[nginx] Modules compatibility: additional upstream metrics.

details: http://hg.nginx.org/nginx/rev/d0d32b33167d branches: changeset: 7219:d0d32b33167d user: Vladimir Homutov <v...@nginx.com> date: Thu Feb 22 17:25:43 2018 +0300 description: Modules compatibility: additional upstream metrics. diffstat: src/http/ngx_http_upstream.h |

Re: DTLS patches

On Wed, Feb 21, 2018 at 10:44:00PM +0800, Wang Shanker wrote: > Hi, > > I noticed that you have introduced `ngx_event_udp_accept()`, which can > create a separate socket for receiving datagrams from a specific client. > I understand that it is necessary for DTLS servers. However I wonder > why it

Re: DTLS patches

elaborate about your environment? Do you proxy DTLS stream directly to backend, or you perform DTLS offload ? What protocol are you using and which server/client software before/behind nginx? I'm attaching refreshed patch against nginx-1.13.9 for those who are interested to test. # HG changeset patch

Re: DTLS patches

On Wed, Feb 21, 2018 at 12:18:27PM +0800, Wang Shanker wrote: > Hi, Vladimir > > `ngx_stream_ssl_init_connection` trys to set tcp_nodelay on the given > connection. > The following patch adds a test for the type of connection before set. > > Cheers, > > Miao Wang > > diff --git

[nginx] Core: added a stub for additional zone configuration.

details: http://hg.nginx.org/nginx/rev/fc4d82c13c04 branches: changeset: 7205:fc4d82c13c04 user: Vladimir Homutov <v...@nginx.com> date: Thu Feb 15 16:08:05 2018 +0300 description: Core: added a stub for additional zone configuration. diffstat: src/core/ngx_cycle.h | 1 + 1

Re: nginx development guide

07.06.2017 17:00, 胡聪 (hucc) пишет: > Hello, > > There are two possible errors in > http://nginx.org/en/docs/dev/development_guide.html#http_load_balancing > >> init(r, us) — initializes per-request ngx_http_upstream_peer_t.peer (not to >> be confused with the >>

Re: [PATCH] Add RFC5424 syslog support

On Fri, May 26, 2017 at 11:20:01AM +0800, Sepherosa Ziehau wrote: > Hi all, > > Any update on this? > Hi, nginx deliberately supports just RFC 3164 and not any later version to keep things simple. supporting just parts of later standard seems quite strange and misleading to me.

Re: DTLS patches

On Thu, May 18, 2017 at 10:29:16AM -0400, George wrote: > thanks for sharing. Is it necessary to compile with --with-debug ? > no, it will work without debug as well ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

DTLS патчи

Привет, Для заинтересованных в тестировании поддержки DTLS, теперь доступен экспериментальный патч: http://nginx.org/patches/dtls/ Подробности в README.txt По результатам можно отписаться в этом треде (а лучше сразу в аналогичном в английской рассылке, чтобы не дублировать)

DTLS patches

Hello all, For all those interested in testing DTLS support, experimental patch is now available at http://nginx.org/patches/dtls/ Check the README.txt for details . If you have any feedback, please report to this thread. ___ nginx mailing list

Re: Proxying UDP: Preserve proxy port during DTLS handshake

On Wed, Apr 12, 2017 at 03:53:43PM -0400, SebK wrote: > Hello everyone, Hi Sebastian, [...] > > So my conclusive question is: Does nginx provide a way to preserve its > chosen dynamic port when forwarding udp packets? > No, currently it is not supported. See also

[nginx] Stream: configurable socket buffer sizes.

details: http://hg.nginx.org/nginx/rev/d7ce41bdf050 branches: changeset: 6975:d7ce41bdf050 user: Vladimir Homutov <v...@nginx.com> date: Mon Apr 03 17:29:19 2017 +0300 description: Stream: configurable socket buffer sizes. The "rcvbuf" and "sndbuf" pa

[nginx] Mail: configurable socket buffer sizes.

details: http://hg.nginx.org/nginx/rev/6c13008ad503 branches: changeset: 6976:6c13008ad503 user: Vladimir Homutov <v...@nginx.com> date: Mon Apr 03 17:30:34 2017 +0300 description: Mail: configurable socket buffer sizes. The "rcvbuf" and "sndbuf" pa

Re: UDP TLS Termination

On Tue, Mar 28, 2017 at 12:25:35PM +0300, Vladimir Homutov wrote: > instead of normal DTLS. i meant SSL (TLS) of course. ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: UDP TLS Termination

On Tue, Mar 28, 2017 at 05:18:54AM -0400, freel wrote: > Hi guys, > > We are interested in UDP TLS Termination, any updates about this feature? I > think I saw such topic on forum few moths ago, but I'm unable to find it > now. > Can you please describe your use-case? Which applications do you

Re: host not found in upstream: не появилась возможность игнорировать?

On 16.03.2017 22:19, obolobova wrote: У нас так не получается, увы - мы используем оверлей с внешним хранилищем (Консулом), а эта разновидность сети требует уникальных имен всех нод в кластере. Да и не хочется ставить старт NGINXа, который служит entrypoint'ом для всех сервисов, в зависимость

Re: Nginx reverse proxy for TFTP UDP port 69 traffic

On 08.03.2017 00:21, Eric Feldhusen wrote: I’m trying to use Nginx to reverse proxy TFTP UDP port 69 traffic and I”m having a problem with getting files through the nginx reverse proxy. My configuration is simple, I’m running TFTP on one Centos 6.x server and the Nginx reserve proxy on another

Re: 答复: Re: having nginx listen the same port more than once

On Tue, Feb 14, 2017 at 04:09:10PM +0800, he.hailo...@zte.com.cn wrote: > now I understand the duplicate listen ports configured in the http > block can be used to implement virtual hosts. > > > but what's the purpose to allow this in the stream block? in my > practise (with 1.9.15.1), nginx will

Re: nginx development guide

On Mon, Feb 13, 2017 at 07:24:05PM +0300, Andrey Kulikov wrote: > Hooray! > > What the doctor ordered. > Looking forward for more parts, especially dedicated to chains > management and corresponding API description. > > So far saw a possible typo: > In section "I/O events": > > that the functions

nginx development guide

Добрый день! Мы рады поделиться с вами первыми результатами наших усилий по созданию документации для разработчиков nginx: руководством разработчика [1] (en) Конечно, руководство не полностью закончено, надеемся, будут и другие части. Будем рады любым вашим комментариям. [1]

nginx development guide

Hello all! We are glad to share with first results of our ongoing efforts to create documentation for nginx developers: the development guide document [1]. The guide is not yet 100% complete and more parts to follow. Of course, your feedback is welcome. [1]

[nginx] Upstream: removed compatibility shims from ngx_http_upstream_t.

details: http://hg.nginx.org/nginx/rev/7113b9b2dd6c branches: changeset: 6881:7113b9b2dd6c user: Vladimir Homutov <v...@nginx.com> date: Wed Jan 25 15:39:22 2017 +0300 description: Upstream: removed compatibility shims from ngx_http_upstream_t. The type is no longer mo

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/b14d4e5a123f branches: changeset: 6880:b14d4e5a123f user: Vladimir Homutov <v...@nginx.com> date: Thu Jan 26 11:44:55 2017 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 del

[nginx] Stream: client SSL certificates were not checked in some cases.

details: http://hg.nginx.org/nginx/rev/1818acd8442f branches: changeset: 6871:1818acd8442f user: Vladimir Homutov <v...@nginx.com> date: Thu Jan 19 16:20:07 2017 +0300 description: Stream: client SSL certificates were not checked in some cases. If ngx_stream_ssl_init_conn

[nginx] Stream: fixed handling of non-ssl sessions.

details: http://hg.nginx.org/nginx/rev/0a08a8babf53 branches: changeset: 6870:0a08a8babf53 user: Vladimir Homutov <v...@nginx.com> date: Thu Jan 19 16:17:05 2017 +0300 description: Stream: fixed handling of non-ssl sessions. A missing check could cause ngx_stream_ssl_h

[nginx] Stream: avoid infinite loop in case of socket read error.

details: http://hg.nginx.org/nginx/rev/ee3645078759 branches: changeset: 6868:ee3645078759 user: Vladimir Homutov <v...@nginx.com> date: Wed Jan 11 12:01:56 2017 +0300 description: Stream: avoid infinite loop in case of socket read error. diffstat: src/

Re: stream module on 100% cpu load

03.01.2017 16:20, A. Schulze пишет: > > Hello, > > last days I setup a server to encapsulate DNS over TLS. > >- DNS-Server @localhost, Port 53 TCP >- NGINX Stream module on public IP, Port 853 TCP, SSL enabled. > > That work so far. > Now I thought to scan this setup using ssllabs.com

[nginx] Stream: client SSL certificates verification support.

details: http://hg.nginx.org/nginx/rev/41cb1b64561d branches: changeset: 6850:41cb1b64561d user: Vladimir Homutov <v...@nginx.com> date: Tue Dec 20 12:05:14 2016 +0300 description: Stream: client SSL certificates verification support. New directives: "ssl_ve

[nginx] Core: show file contents only once while dumping configuration.

details: http://hg.nginx.org/nginx/rev/1bf4f21b1b72 branches: changeset: 6776:1bf4f21b1b72 user: Vladimir Homutov <v...@nginx.com> date: Tue Oct 18 16:33:38 2016 +0300 description: Core: show file contents only once while dumping configuration. Files are considered th

Re: похоже на багу с syslog nginx

14.10.2016 16:33, Иван Мишин пишет: > Не ужели никто не в курсе почему nginx не отправляет access логи в > случае описанном выше? > для начала: 1) проверьте логи 2) проверьте tcpdump'ом на той машине, где nginx, чтобы исключить разного рода проблемы с сетью > 7 октября 2016 г., 17:44

[nginx] Upstream hash: fixed missing upstream name initialization.

details: http://hg.nginx.org/nginx/rev/52367732bcbc branches: changeset: 6697:52367732bcbc user: Vladimir Homutov <v...@nginx.com> date: Fri Sep 16 15:13:24 2016 +0300 description: Upstream hash: fixed missing upstream name initialization. diffstat: src/http/m

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/4bce3edfac2c branches: changeset: 6691:4bce3edfac2c user: Vladimir Homutov <v...@nginx.com> date: Thu Sep 15 14:56:26 2016 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 del

[nginx] Stream: phases.

details: http://hg.nginx.org/nginx/rev/3908156a51fa branches: changeset: 6693:3908156a51fa user: Roman Arutyunyan date: Thu Sep 15 14:55:54 2016 +0300 description: Stream: phases. diffstat: src/stream/ngx_stream.c | 110

[nginx] Stream: ssl_preread module.

details: http://hg.nginx.org/nginx/rev/060d71292b69 branches: changeset: 6695:060d71292b69 user: Vladimir Homutov <v...@nginx.com> date: Thu Sep 15 14:56:51 2016 +0300 description: Stream: ssl_preread module. The ssl_preread module extracts information from the SSL Client

[nginx] Stream: preread phase.

details: http://hg.nginx.org/nginx/rev/ea9dfe2f62e7 branches: changeset: 6694:ea9dfe2f62e7 user: Vladimir Homutov <v...@nginx.com> date: Thu Sep 15 14:56:02 2016 +0300 description: Stream: preread phase. In this phase, head of a stream is read and analysed before proc

[nginx] Stream: filters.

details: http://hg.nginx.org/nginx/rev/56fc55e32f23 branches: changeset: 6692:56fc55e32f23 user: Roman Arutyunyan date: Thu Sep 15 14:55:46 2016 +0300 description: Stream: filters. diffstat: auto/modules|6 +- auto/sources

[nginx] Stream: log module.

details: http://hg.nginx.org/nginx/rev/0125b151c9a5 branches: changeset: 6678:0125b151c9a5 user: Vladimir Homutov <v...@nginx.com> date: Mon Sep 05 17:50:16 2016 +0300 description: Stream: log module. diffstat: auto/modules | 2 + src/stream/ngx_st

[nginx] Stream: the $upstream_addr variable.

details: http://hg.nginx.org/nginx/rev/ab9b4fd8c5b7 branches: changeset: 6675:ab9b4fd8c5b7 user: Vladimir Homutov <v...@nginx.com> date: Fri Sep 02 18:27:05 2016 +0300 description: Stream: the $upstream_addr variable. Keeps the full address of the upstream server. If s

[nginx] Stream: $upstream_bytes_sent and $upstream_bytes_received.

details: http://hg.nginx.org/nginx/rev/df3a7c029dec branches: changeset: 6676:df3a7c029dec user: Vladimir Homutov <v...@nginx.com> date: Fri Sep 02 18:27:08 2016 +0300 description: Stream: $upstream_bytes_sent and $upstream_bytes_received. diffstat: src/

[nginx] Stream: the $bytes_received variable.

details: http://hg.nginx.org/nginx/rev/5e2821c2de46 branches: changeset: 6668:5e2821c2de46 user: Vladimir Homutov <v...@nginx.com> date: Fri Aug 26 15:33:02 2016 +0300 description: Stream: the $bytes_received variable. The variable keeps the number of bytes received from the

[nginx] Stream: the $session_time variable.

details: http://hg.nginx.org/nginx/rev/164a0824ce20 branches: changeset: 6669:164a0824ce20 user: Vladimir Homutov <v...@nginx.com> date: Fri Aug 26 15:33:04 2016 +0300 description: Stream: the $session_time variable. The variable keeps time spent on processing the stream s

[nginx] Stream: the $protocol variable.

details: http://hg.nginx.org/nginx/rev/c6372a40c2a7 branches: changeset: 6670:c6372a40c2a7 user: Vladimir Homutov <v...@nginx.com> date: Fri Aug 26 15:33:07 2016 +0300 description: Stream: the $protocol variable. The variable keeps protocol used by the client, "T

[nginx] Upstream: the $upstream_bytes_received variable.

details: http://hg.nginx.org/nginx/rev/c131f20c9562 branches: changeset: 6654:c131f20c9562 user: Vladimir Homutov <v...@nginx.com> date: Wed Aug 10 16:46:39 2016 +0300 description: Upstream: the $upstream_bytes_received variable. Unlike $upstream_response_length that only

[nginx] Version bump.

details: http://hg.nginx.org/nginx/rev/0b4249f975eb branches: changeset: 6647:0b4249f975eb user: Vladimir Homutov <v...@nginx.com> date: Tue Jul 26 19:07:18 2016 +0300 description: Version bump. diffstat: src/core/nginx.h | 4 ++-- 1 files changed, 2 insertions(+), 2 del

[nginx] Fixed regex captures handling without PCRE.

details: http://hg.nginx.org/nginx/rev/af642539cd53 branches: changeset: 6644:af642539cd53 user: Vladimir Homutov <v...@nginx.com> date: Wed Jul 06 14:33:40 2016 +0300 description: Fixed regex captures handling without PCRE. If PCRE is disabled, captures were treated as

[nginx] Stream: style.

details: http://hg.nginx.org/nginx/rev/8ed51b02f655 branches: changeset: 6629:8ed51b02f655 user: Vladimir Homutov <v...@nginx.com> date: Tue Jul 12 17:34:40 2016 +0300 description: Stream: style. diffstat: src/stream/ngx_stream_limit_conn_module.c | 2 +- src/

<    1   2   3   >