Hello,
On Mon, 17 Jun 2024 10:22:24 +0100
Kirill A. Korinsky wrote:
> On Mon, 17 Jun 2024 00:21:27 +0100,
> J Carter wrote:
> >
> > Well *I* quite agree.
> >
> > I would also suggest that as DNS functionality in nginx is strictly
> > limited to resolving as
Hello,
On Sun, 16 Jun 2024 10:07:28 +0100
Kirill A. Korinsky wrote:
> On Sun, 16 Jun 2024 02:45:15 +0100,
> J Carter wrote:
> >
> > Sounds familiar :)
> >
> > https://mailman.nginx.org/pipermail/nginx-devel/2022-May/YQ3MYP4VNQYWEJS3XYLPMU4HZUKS4PYF.html
>
&
On Sun, 16 Jun 2024 04:29:51 +0300
Maxim Dounin wrote:
> Hello!
>
> On Sat, Jun 15, 2024 at 12:02:28PM +0100, Kirill A. Korinsky wrote:
>
> > Greetings,
> >
> > Here a trivial patch which allows DNS responses with enabled AD bit
> > from used resolver.
> >
> > Index: src/core/ngx_resolver.c
Hello,
On Thu, 13 Jun 2024 16:05:18 +0100
Kirill A. Korinsky wrote:
> On Mon, 10 Jun 2024 09:56:05 +0100,
> Martin Kjær Jørgensen via nginx wrote:
> >
> >
> > Is this possible without hacking nginx sources or manipulative intermediate
> > proxies?
> >
>
> As you may see in
:53:46PM +0100, J Carter wrote:
> > Hello Sergey,
> >
> > On Mon, 27 May 2024 14:21:43 +0400
> > Sergey Kandaurov wrote:
> >
> > > # HG changeset patch
> > > # User Sergey Kandaurov
> > > # Date 1716805272 -14400
On Tue, 11 Jun 2024 02:46:13 +0100
J Carter wrote:
> Style cleanup of previous patch.
>
> Also removed 'status already
> returned' guard in slice range variable handler, as it is no longer
> needed given other changes in patch.
>
Additional fixes.
# HG changeset patch
# Use
Style cleanup of previous patch.
Also removed 'status already
returned' guard in slice range variable handler, as it is no longer
needed given other changes in patch.
# HG changeset patch
# User J Carter
# Date 1718069043 -3600
# Tue Jun 11 02:24:03 2024 +0100
# Node ID
# HG changeset patch
# User J Carter
# Date 1717886685 -3600
# Sat Jun 08 23:44:45 2024 +0100
# Node ID 1b8a60f7640be4a900ac77d8022b7d8cc6944186
# Parent 02e9411009b987f408214ab4a8b6b6093f843bcd
Slice filter: proxy_cache_background_update support (ticket #1348).
Previously, subrequests
Hello Sergey,
On Mon, 27 May 2024 14:21:43 +0400
Sergey Kandaurov wrote:
> # HG changeset patch
> # User Sergey Kandaurov
> # Date 1716805272 -14400
> # Mon May 27 14:21:12 2024 +0400
> # Node ID e82a7318ed48fdbc1273771bc96357e9dc232975
> # Parent f58b6f6362387eeace46043a6fc0bceb56a6786a
Hello,
[...]
> ```
> The goal is to bypass SSO if a correct HTTP Basic Auth header is present
> while making sure connections are only from said IPs.
>
> When I disable the IP check it works flawlessly. How could I separate these
> requirements?
>
> So (SSO or Basic Auth) and Correct IP
Fixed a typo in patch description, and overlooked buffer overflow...
# HG changeset patch
# User J Carter
# Date 1716779649 -3600
# Mon May 27 04:14:09 2024 +0100
# Node ID e2ebeb2b05062369626e2de1ba753f318f821d9c
# Parent f58b6f6362387eeace46043a6fc0bceb56a6786a
Memcached
# HG changeset patch
# User J Carter
# Date 1716779649 -3600
# Mon May 27 04:14:09 2024 +0100
# Node ID e90301dd1516b6dfa5b2b0beec05cfe2b567ea1e
# Parent f58b6f6362387eeace46043a6fc0bceb56a6786a
Memcached: memcached_flags_set directive.
This directive creates a variable that returns
Hello,
On Sun, 19 May 2024 16:47:02 -0400
Saint Michael wrote:
> I need some help with a Nginx,. Twitter problem
> please open a twitter client x.com
> and post this link
> https://patrician.org/22a51cfb-7d5b-4a97-a687-a10cd1946766/
> and then open a new client and post
>
On Wed, 6 Mar 2024 19:36:32 +0400
Sergey Kandaurov wrote:
> > On 28 Feb 2024, at 05:24, Piotr Sikora via nginx-devel
> > wrote:
> >
> > # HG changeset patch
> > # User Piotr Sikora
> > # Date 1708977643 0
> > # Mon Feb 26 20:00:43 2024 +
> > # Branch patch017
> > # Node ID
Hello,
On Tue, 5 Mar 2024 13:07:53 -0800
"li...@lazygranch.com" wrote:
> I am presently using a scheme like this to prevent scraping documents.
>
>location /images/ {
> valid_referers none blocked www.example.com example.com
>
Hello,
On Thu, 7 Mar 2024 08:17:23 +0200
Clima Gabriel wrote:
> Greetings,
> I'm investigating a bug, super easy to reproduce.
> Thought you might be curious.
>
> Minimal Nginx config. Create two files. 100M and 1M:
> dd if=/dev/zero of=/var/www/file100M bs=100M count=1
> dd if=/dev/zero
Hello Taco,
On Sat, 2 Mar 2024 09:54:46 -0300
Taco de Wolff wrote:
> Thank you Jordan for the response.
>
No problem.
> Including the SNI information in cURL works, thank you. I wasn't aware this
> was so very different from TCP/HTTP2.
>
> The point I was trying to make about the
Hello,
On Wed, 28 Feb 2024 21:45:37 -0300
Taco de Wolff wrote:
> Hi,
>
> I've noticed at least in 1.24.0 and 1.25.4 that adding an
> ssl_reject_handshake to the default server breaks SNI for other
> servers. Example:
>
> ```
> server {
> server_name _;
> listen 80 default_server;
>
Hello,
On Mon, 26 Feb 2024 09:55:10 +0100
"Roberto D. Maggi" wrote:
> Hi you all,
>
> I'm trying to improve the reverse proxy's virtual hosts' configuration
> files of my company,
>
> but I'm facing an issue that I can't understand:
>
>
> In the "location / " block I inserted these lines
>
Hello Roman,
On Wed, 21 Feb 2024 17:29:52 +0400
Roman Arutyunyan wrote:
> Hi,
>
[...]
> Checking whether the address used in PROXY writer is in fact the address
> that was passed in the PROXY header, is complicated. This will either require
> setting a flag when PROXY address is set by
Hello,
On Tue, 20 Feb 2024 11:57:27 +0800
Kin Seng wrote:
> Hi J Carter,
>
> Thank you for your reply.
> I am capturing the packet from firewall, and the filtering is as per below
> for the previously attached pcap.
I see, I assumed you had run tcpdump on the nginx
host. I'd
Hello,
On Tue, 20 Feb 2024 09:40:13 +0800
Kin Seng wrote:
> Hi J Carter,
>
> This is the only results from the whole 5 minutes session (intentionally
> without any transaction to create inactivity). Is there any symptoms which
> can prove that other parties are the one who Initi
Hello,
On Fri, 16 Feb 2024 14:19:57 +0300
izor...@gmail.com wrote:
> Hello.
>
> Patch to update current MIME types.
> Most of information is taken from IANA and Wikipedia.
>
>
It might be a good idea to provide a reason for each of these mime type
changes, such as what real problem this
Hello,
On Mon, 19 Feb 2024 16:24:48 +0800
Kin Seng wrote:
[...]
> Please refer to the attachments for reference.
>
> On Mon, Feb 19, 2024 at 4:24 PM Kin Seng wrote:
> > After capturing the tcp packet and check via wireshark, I found out that
> > the nginx is sending out the RST to the public
On Tue, 6 Feb 2024 00:44:56 +
J Carter wrote:
> On Tue, 6 Feb 2024 00:16:31 +
> J Carter wrote:
>
> > Hello,
> >
> > On Mon, 5 Feb 2024 23:24:39 +0200
> > Clima Gabriel wrote:
> >
> > > Hello everyone,
> > >
On Tue, 6 Feb 2024 00:16:31 +
J Carter wrote:
> Hello,
>
> On Mon, 5 Feb 2024 23:24:39 +0200
> Clima Gabriel wrote:
>
> > Hello everyone,
> >
> > (the code is probably clearer and attached below)
> > This function modifies what ngx_connection_t->
Hello,
On Mon, 5 Feb 2024 23:24:39 +0200
Clima Gabriel wrote:
> Hello everyone,
>
> (the code is probably clearer and attached below)
> This function modifies what ngx_connection_t->data points to.
> ngx_connection_t->data is initially *ngx_http_connection_t.
> The *ngx_http_connection_t is
Hello,
On Thu, 1 Feb 2024 12:28:40 -0500
Larry Martell wrote:
> On Thu, Feb 1, 2024 at 11:57 AM Sergey A. Osokin wrote:
> >
> > Hi Larry,
> >
> > On Thu, Feb 01, 2024 at 11:34:08AM -0500, Larry Martell wrote:
> > > We run Ubuntu 20.04, which has nginx 1.18. I was asked to upgrade it
> > > to
Hello,
On Thu, 25 Jan 2024 14:53:51 +0100
Ľuboš Pinteš wrote:
> Hello Jason and thank for your reply.
>
> I am fairly new to this stuff.
>
> Concerning health checks, does it matter if I have only one simple
> server? So no load balancing etc.?
>
Just so you know, active health checks (on
Hello,
On Sat, 27 Jan 2024 15:55:42 +0530
Rakshith Kumar wrote:
> Hello Team,
>
> I would like to know how to limit the NGINX limit size.
> We would like to set size limit for Nginx log files on App Volumes Manager
> since it consume disk space over time. Can we add any parameters to
>
Hello,
On Fri, 26 Jan 2024 16:28:15 -0300
Renato Botelho wrote:
> Hello!
>
> I'm building nginx on an environment with openssl 3.2.0 and some SSL
> tests are failing. I suspect it's related to openssl version because it
> works on another env with older openssl. But maybe I'm wrong.
>
>
Hello,
Thanks for the feedback.
On Wed, 24 Jan 2024 12:20:59 +0300
Maxim Dounin wrote:
> Hello!
>
> On Sun, Jan 21, 2024 at 10:37:24AM +, J Carter wrote:
>
> > # HG changeset patch
> > # User J Carter
> > # Date 1705832811 0
> > # Sun Jan
# HG changeset patch
# User J Carter
# Date 1705832811 0
# Sun Jan 21 10:26:51 2024 +
# Node ID b00332a5253eefb53bacc024c72f55876c2eac6e
# Parent ee40e2b1d0833b46128a357fbc84c6e23be9be07
SSL: Added SSLKEYLOGFILE key material to debug logging.
This patch also introduces the debug_keylog
Hello,
On Tue, 9 Jan 2024 08:59:14 +0300
Maxim Dounin wrote:
> Hello!
>
> On Mon, Jan 08, 2024 at 01:31:11PM +, J Carter wrote:
>
> > On Mon, 8 Jan 2024 11:25:55 +
> > J Carter wrote:
> >
> > > Hello,
> > >
> > > On
On Mon, 8 Jan 2024 11:25:55 +
J Carter wrote:
> Hello,
>
> On Mon, 27 Nov 2023 05:50:27 +0300
> Maxim Dounin wrote:
>
> > # HG changeset patch
> > # User Maxim Dounin
> > # Date 1701050170 -10800
> > # Mon N
Hello,
On Mon, 27 Nov 2023 05:50:27 +0300
Maxim Dounin wrote:
> # HG changeset patch
> # User Maxim Dounin
> # Date 1701050170 -10800
> # Mon Nov 27 04:56:10 2023 +0300
> # Node ID 00c3e7333145ddb5ea0eeaaa66b3d9c26973c9c2
> # Parent 61d08e4cf97cc073200ec32fc6ada9a2d48ffe51
> AIO
Hello,
On Fri, 29 Dec 2023 09:54:30 -0300
Rejaine Monteiro wrote:
> Hi all,
>
> I´m running Nginx community edition and need to implement rate limiting
>
> There's plenty of guides out there on how to do this, but no guides on how
> to get real values/stats from the access logs
>
>
> What I
# HG changeset patch
# User J Carter
# Date 1703993644 0
# Sun Dec 31 03:34:04 2023 +
# Node ID 1eaf9f76184f849fb21c5d2d543f2aa2df3be40c
# Parent ee40e2b1d0833b46128a357fbc84c6e23be9be07
Image filter: fixed sharpen parsing.
Previously non numeric values were read as 0. This patch makes
On Thu, 28 Dec 2023 17:23:38 +0300
Vladimir Homutov via nginx-devel wrote:
> On Thu, Dec 28, 2023 at 04:31:41PM +0300, Maxim Dounin wrote:
> > Hello!
> >
> > On Wed, Dec 27, 2023 at 04:17:38PM +0300, Vladimir Homutov via nginx-devel
> > wrote:
> >
> > > On Wed, Dec 27, 2023 at 02:48:04PM
Hello,
Thanks for the review and feedback.
On Tue, 26 Dec 2023 19:07:37 +0400
Sergey Kandaurov wrote:
> > On 26 Nov 2023, at 03:37, J Carter wrote:
> >
> > # HG changeset patch
> > # User J Carter
> > # Date 1700949429 0
> > # Sat Nov
Hello,
On Fri, 22 Dec 2023 12:05:51 +0530
Akash Shrivastava wrote:
> Hi there,
> Urgent support needed on Nginx-ingress 3.4.0
I'd recommend posting ingress controller related questions on the
discussions section of it's Github repo.
https://github.com/nginxinc/kubernetes-ingress/discussions
Hello,
Thanks the review and feedback.
On Sat, 16 Dec 2023 05:57:28 +0300
Maxim Dounin wrote:
> Hello!
>
> On Sat, Dec 09, 2023 at 08:42:11AM +, J Carter wrote:
>
> > On Sat, 09 Dec 2023 07:46:10 +
> > J Carter wrote:
> >
> > > # H
On Wed, 13 Dec 2023 02:45:54 +
J Carter wrote:
> Hello,
>
> On Tue, 12 Dec 2023 16:17:11 +0100
> Jérôme Loyet wrote:
>
> > Hello,
> >
> > I'm trying to serve some files from /proc but nginx return a 0 bytes
> > content because the file size o
Hello,
On Tue, 12 Dec 2023 16:17:11 +0100
Jérôme Loyet wrote:
> Hello,
>
> I'm trying to serve some files from /proc but nginx return a 0 bytes
> content because the file size of many files in /proc/ tree is simply 0 by
> design.
That is correct, reading Virtual File System files would
On Sat, 09 Dec 2023 07:46:10 +
J Carter wrote:
> # HG changeset patch
> # User J Carter
> # Date 1702101635 0
> # Sat Dec 09 06:00:35 2023 +
> # Node ID 1a77698f82d2580aa8b8f62ce89b4dbb6d678c5d
> # Parent d9275e982a7188a1ea7855295ffa93362ea9830f
> Win32: exte
# HG changeset patch
# User J Carter
# Date 1702098547 0
# Sat Dec 09 05:09:07 2023 +
# Node ID d9275e982a7188a1ea7855295ffa93362ea9830f
# Parent f366007dd23a6ce8e8427c1b3042781b618a2ade
Events: debug_random directive
This directive enables debug logging for only a percentage
This patch series reworks previous proposal for debug_random directive,
with (re)consideration for advice on unessecary complexity.
(see mailing list, August 2nd 2023)
https://mailman.nginx.org/pipermail/nginx-devel/2023-August/BQNBXJFIIHFLHRE2ASU4QHPTMWPJUP5D.html
Resubmitting as a series due
it on in case you need it.
On Sat, 25 Nov 2023 16:03:37 +0800
Zero King wrote:
> Hi Jordan,
>
> Thanks for your suggestion. I will give it a try and also try to push
> our K8s team to implement a firewall if possible.
>
> On 20/11/23 10:33, J Carter wrote:
> > Hello,
> >
Hi Brad,
I'd recommend raising your concern the NIC Github repo's issue tracker.
https://github.com/nginxinc/kubernetes-ingress/issues
On Fri, 8 Dec 2023 04:55:12 +
Brad Bishop via nginx wrote:
> Hi Folks,
>
> We're using NGINX Ingress Controller 3.0.2 (NGINX 1.23.3) in AKS on a couple
Hello Roman,
Thank you for the review and feedback.
On Mon, 27 Nov 2023 16:18:21 +0400
Roman Arutyunyan wrote:
> Hi Jordan,
>
> On Thu, Nov 23, 2023 at 02:52:55PM +, J Carter wrote:
> > # HG changeset patch
> > # User J Carter
> > # Date 1700751016 0
> >
# HG changeset patch
# User J Carter
# Date 1700949429 0
# Sat Nov 25 21:57:09 2023 +
# Node ID 98306e705015758eab0a05103d90e6bdb1da2819
# Parent f366007dd23a6ce8e8427c1b3042781b618a2ade
Proxy: altered limit_rate to support variables
diff -r f366007dd23a -r 98306e705015 src/http
if possible.
>
> On 20/11/23 10:33, J Carter wrote:
> > Hello,
> >
> > A self contained solution would be to double proxy, first through nginx
> > stream server
> > and then locally back to nginx http server (with proxy_pass via unix
> > socket, or to
> &g
# HG changeset patch
# User J Carter
# Date 1700751016 0
# Thu Nov 23 14:50:16 2023 +
# Node ID cc79903ca02eff8aa87238a0f801f8070425d9ab
# Parent 7ec761f0365f418511e30b82e9adf80bc56681df
Added merge inheritance to proxy_set_header
This patch introduces 'inherit' argument
Hello,
A self contained solution would be to double proxy, first through nginx stream
server and then locally back to nginx http server (with proxy_pass via unix
socket, or to localhost on a different port).
You can implement your own custom rate limiting logic in the stream server with
NJS
+1 on "why are you doing this?".
However, to answer the question - rather than spawning a new shell for every
request, use a loop in your bash script that is driven by access log output.
For example.
tail -n0 -f /var/log/nginx/access.log | \
while read;
do echo "one request";
Hello,
Thanks for the review.
> On Mon, Jul 24, 2023 at 05:24:04AM +0100, J Carter wrote:
>
> [..]
>
> > # HG changeset patch
> > # User J Carter
> > # Date 1690171706 -3600
> > # Mon Jul 24 05:08:26 2023 +0100
> > # Node ID ea91b9aa69d
On Tue, 18 Jul 2023 03:36:02 +
J Carter wrote:
> On Sat, 15 Jul 2023 03:48:25 +
> J Carter wrote:
>
> > # HG changeset patch
> > # User J Carter
> > # Date 1689391559 -3600
> > # Sat Jul 15 04:25:59 2023 +0100
> > # Node ID b1ea0a60417e54
On Sat, 15 Jul 2023 03:48:25 +
J Carter wrote:
> # HG changeset patch
> # User J Carter
> # Date 1689391559 -3600
> # Sat Jul 15 04:25:59 2023 +0100
> # Node ID b1ea0a60417e547513654bf9d6bb79714865c780
> # Parent 77c1418916f7817a0d020f28d8a08f278a12fe43
> Added d
# HG changeset patch
# User J Carter
# Date 1689391559 -3600
# Sat Jul 15 04:25:59 2023 +0100
# Node ID b1ea0a60417e547513654bf9d6bb79714865c780
# Parent 77c1418916f7817a0d020f28d8a08f278a12fe43
Added debug_random directive
This directive enforces for EITHER a percentage of total
Hello,
On Mon, 22 May 2023 00:40:08 +0300
Maxim Dounin wrote:
> Hello!
>
> On Sun, May 14, 2023 at 11:59:35PM +0100, J Carter wrote:
>
> > Hello,
> >
> > >On Sun, 14 May 2023 18:48:06 +0100
> > >J Carter wrote:
> >
> > > Hello,
&g
Hello,
Thanks for the reply.
On Mon, 22 May 2023 15:48:23 +0300
Maxim Dounin wrote:
> Hello!
>
> On Sun, May 14, 2023 at 04:51:58AM +0100, J Carter wrote:
>
> > # HG changeset patch
> > # User jordanc.car...@outlook.com
> > # Date 1684035158 -3600
> > #
Hello,
>On Sun, 14 May 2023 18:48:06 +0100
>J Carter wrote:
> Hello,
>
> On Sun, 14 May 2023 17:40:43 +0300
> Maxim Dounin wrote:
>
> > Hello!
> >
> > On Fri, May 12, 2023 at 03:37:52AM +0100, J Carter wrote:
> >
> > > # HG c
On Sun, 14 May 2023 19:09:30 +0100
J Carter wrote:
> Hello,
>
> > On Sun, 14 May 2023 17:33:10 +0300
> > Maxim Dounin wrote:
>
> > Hello!
> >
> > On Sun, May 14, 2023 at 09:55:54AM +0400, Roman Arutyunyan wrote:
> >
> > > Hi Eduard,
Hello,
> On Sun, 14 May 2023 17:33:10 +0300
> Maxim Dounin wrote:
> Hello!
>
> On Sun, May 14, 2023 at 09:55:54AM +0400, Roman Arutyunyan wrote:
>
> > Hi Eduard,
> >
> > On Sat, May 13, 2023 at 10:43:59PM -0600, Eduard Vercaemer wrote:
> > > for some context, I recently I tried configuring
Hello,
On Sun, 14 May 2023 17:40:43 +0300
Maxim Dounin wrote:
> Hello!
>
> On Fri, May 12, 2023 at 03:37:52AM +0100, J Carter wrote:
>
> > # HG changeset patch
> > # User jordanc.car...@outlook.com
> > # Date 1683858766 -3600
> > # Fri May
Re-sending with non-malformed patch...
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1684035158 -3600
# Sun May 14 04:32:38 2023 +0100
# Node ID dad6e472ee0d97a738b117f6480987ef135c9e7f
# Parent b71e69247483631bd8fc79a47cc32b762625b1fb
Added $realip_add_x_forwarded_for
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1684035158 -3600
# Sun May 14 04:32:38 2023 +0100
# Node ID dad6e472ee0d97a738b117f6480987ef135c9e7f
# Parent b71e69247483631bd8fc79a47cc32b762625b1fb
Added $realip_add_x_forwarded_for
Resolves Ticket #2127.
Duplicates the
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1683858766 -3600
# Fri May 12 03:32:46 2023 +0100
# Node ID de1a1b4141e827984cbd0d2feb97f870c32ff289
# Parent b71e69247483631bd8fc79a47cc32b762625b1fb
Added $http2_stream_id
Useful for tracing multiplexed requests from client
On Sun, 7 May 2023 21:55:19 +0100
J Carter wrote:
> # HG changeset patch
> # User jordanc.car...@outlook.com
> # Date 1683491710 -3600
> # Sun May 07 21:35:10 2023 +0100
> # Node ID e1ec9971da677b763c7576c729576d6f906631ae
> # Parent b71e69247483631bd8fc79a47cc32b762625b
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1683491710 -3600
# Sun May 07 21:35:10 2023 +0100
# Node ID e1ec9971da677b763c7576c729576d6f906631ae
# Parent b71e69247483631bd8fc79a47cc32b762625b1fb
Asynchronous close event handling for single peer upstreams
Prevents
Hi,
On 18/04/2023 13:58, mailingl...@unix-solution.de wrote:
Hello,
I have a nginx proxy in front of systemd-nspawn containers.
The IP's of the containers are dynamic.
When I start nginx *after* the containers it works.
When the IP of the container is changed while nginx is running i get a
Hello,
resubmitting with the changes suggested.
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1681067934 -3600
# Sun Apr 09 20:18:54 2023 +0100
# Node ID c8dcf584b36505e42bd2ea2965c1020069adb677
# Parent 5f1d05a21287ba0290dd3a17ad501595b442a194
Asynchronous close event
, Apr 02, 2023 at 06:57:03PM +0100, J Carter wrote:
I've also attached an example nginx.conf and test script that
simulates the asynchronous close events.
Two different test cases can be found within that, one with path
/1 for single peer upstream and /2 for multi-peer.
You should see 2 upstream
re-sending the patch as an attachment as the formatting is still weird,
and fixed typo I spotted..
On 02/04/2023 18:57, J Carter wrote:
Hello,
I've also attached an example nginx.conf and test script that
simulates the asynchronous close events.
Two different test cases can be found within
Hello,
I've also attached an example nginx.conf and test script that simulates the
asynchronous close events.
Two different test cases can be found within that, one with path /1 for single
peer upstream and /2 for multi-peer.
You should see 2 upstream addresses repeated in a row
On 09/02/2023 16:45, Aleksei Bavshin wrote:
On 2/5/2023 7:01 PM, J Carter wrote:
Hi Aleksei,
Why not permanently assign the task of resolving a given upstream
server group (all servers/peers within it) to a single worker?
It seems that this approach would resolve the SRV issues, and remove
Hi Aleksei,
Why not permanently assign the task of resolving a given upstream server
group (all servers/peers within it) to a single worker?
It seems that this approach would resolve the SRV issues, and remove the
need for the shared queue of tasks.
The load would still be spread evenly
Adding the patch file, as something is messing with the formatting of
the patches in email body..
On 28/01/2023 23:15, J Carter wrote:
Hello,
An example of the dark mode and light mode pages is here
https://imgur.com/a/n9QJpp4
# HG changeset patch
# User jordanc.car...@outlook.com
# Date
Hello,
An example of the dark mode and light mode pages is here
https://imgur.com/a/n9QJpp4
# HG changeset patch
# User jordanc.car...@outlook.com
# Date 1674945436 0
# Sat Jan 28 22:37:16 2023 +
# Branch dark-error
# Node ID 0dcba21038765f6f03098cbdf23f401e89e3648f
# Parent
It's trivial to do with error page OP as mentioned - an example:
limit_req_status 598;
limit_req_zone $binary_remote_addr zone=a:1m rate=1r/m;
server {
limit_req zone=a nodelay;
error_page 598 = @send-204;
location / {
...
}
ex_value = >cvr;
+
+ if (ngx_http_compile_complex_value() != NGX_OK) {
+ return NGX_CONF_ERROR;
+ }
+
+ if (ctx->cvr.lengths != NULL) {
+ continue;
+ }
+
len = value[i].len;
p = value[i].da
Hello,
Please find below my revised patch with style and code bug fixes
included. The only change in behavior of note is that invalid rate
values are now simply ignored in the same fashion an empty key is, and
the use of the parsing of complex value being disabled if a non variable
is used
Hello,
Thanks again for your reply and thoughts.
On 02/01/2023 23:47, Maxim Dounin wrote:
Hello!
On Mon, Jan 02, 2023 at 06:21:03AM +, J Carter wrote:
"The fundamental problem with dynamic rates in limit_req, which is
a leaky bucket limiter, is that the rate is a property which
ap
states which can be stored there?
A persistent record of the rate that was last assigned to a given
node/state is needed exclusively for expiring records (in the expire
function). I don't believe this can be avoided, as the rate of the
current request is unrelated to the 'to be removed'
Hello,
Please find below a patch to enable dynamic rate limiting for limit_req module.
/* EXAMPLE-*/
geo $traffic_tier {
defaultfree;
127.0.1.0/24 basic;
127.0.2.0/24 premium;
}
map
85 matches
Mail list logo
