Re: nginx Digest, Vol 178, Issue 2

On Tue, Jul 8, 2025 at 1:25 AM Ian Hobson wrote: > I do hope they taught you that dividing by zero was impossible/ did not > work/was not allowed. > > On 08/07/2025 04:46, Mark Mielke wrote: > > like how in primary grade school they might teach that divided by zero > > equals zero, > Much outsid

Re: nginx Digest, Vol 178, Issue 3

Sorry for the noise guys. Tobiass those links you provided were just what I needed. Thank you so much for taking the time to help me. ___ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx

Re: nginx Digest, Vol 178, Issue 3

> When replying, please edit your Subject line so it is more specific > than "Re: Contents of nginx digest..." > > > Today's Topics: > >1. Re: nginx Digest, Vol 178, Issue 2 (Matthew Ngaha) >2. Re: nginx Digest, Vol 178, Issue 2 (bruce) >3. Re

Re: how to unsubscribe?

On Mon, Jul 7, 2025 at 5:53 PM Rostyslav Zalevskyy wrote: > > How can I unsubscribe it ? > > ___ > nginx mailing list > nginx@nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx Visit the link at the bottom of the email you receive. ___

Re: nginx Digest, Vol 178, Issue 2

Also, words mean things. When one doesn't understand the words it is easy to presume that it could be explained more simply, but actually it can be explained less accurately. If the target of the document is people with no background, it may be important to stick to the basics and gloss over compl

Re: nginx Digest, Vol 178, Issue 2

Hi Matthew, I can still remember when I was a n00b, so I'll show some mercy here. 1.) Learn how to email. You can start by providing a meaningful and descriptive subject and checking if you actually want to send an email before doing so. 2.) Learn how to google. I did a quick "opensuse

Re: nginx Digest, Vol 178, Issue 2

hi. part of what happens in some software, is that the docs are either hard to comprehend for the beginner, the docs require other docs, which require... , or docs don't really exist!! writing good clear docs with examples at a level that beginners grasp, and keeping updated docs is a beast!!..

Re: nginx Digest, Vol 178, Issue 2

Like I said, those explanations are for people with Linux/programming knowledge. I'm struggling to understand what's being said. I.e this sentence is hard to comprehend: """Variables are e.g. useful for related repositories like packman (http://ftp.gwdg.de/pub/linux/packman/suse/$releasever), whic

Re: nginx Digest, Vol 178, Issue 1

behalf of Matthew Ngaha Sent: 06 July 2025 23:02 To: nginx@nginx.org Subject: Re: nginx Digest, Vol 178, Issue 1 CAUTION: This email has been sent from an external source. Do not click links, open attachments, or provide sensitive business information unless you can verify the sender’s legitimacy

Re: nginx Digest, Vol 178, Issue 1

person managing the list at > nginx-ow...@nginx.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of nginx digest..." > > > Today's Topics: > > 1. nginx-1.29.

Re: Re:

Perhaps start here instead? https://nginx.org/en/docs/install.html From: nginx on behalf of Matthew Ngaha Sent: 06 July 2025 21:01 To: nginx@nginx.org Subject: Re: CAUTION: This email has been sent from an external source. Do not click links, open

Re:

Sorry I forgot to include a title for the email. On Sun, Jul 6, 2025 at 8:31 PM Matthew Ngaha wrote: > > Hi all. I want to learn Nginx. I haven't started the tutorial yet but > I had an earlier edition back in the day. The tutor advises to install > Nginx from source. Is this a good way to instal

Re: Issue with SSE and fcgiwrap in nginx (RESTCONF)

Hi Sergey, Could you please: > > - share the `/etc/nginx/nginx.conf' configuration file; > - describe how do you run `fcgiwrap', please provide as much > as much details as you can; do not forget to share its > configuration file as well. > > Also, are you using `spawn-fcgi'? If so, please pr

Re: Issue with SSE and fcgiwrap in nginx (RESTCONF)

Hi Rostyslav, thanks for the update. On Thu, May 15, 2025 at 04:24:36PM -0700, Rostyslav Zalevskyy wrote: > On Thu, May 15, 2025 at 3:08 AM Sergey A. Osokin wrote: > > > Also, I've found there's the nginx, version 1.18.0, there. > > Would you mind to reproduce the issue with more recent stable v

Re: Issue with SSE and fcgiwrap in nginx (RESTCONF)

Hi Rostyslav, On Wed, May 14, 2025 at 04:59:20PM -0700, Rostyslav Zalevskyy wrote: > On Wed, May 14, 2025 at 2:31 AM Sergey A. Osokin wrote: > > > [...] > > > > Is there a chance to build nginx with a debugging log as described on > > the following page, https://nginx.org/en/docs/debugging_log.h

Re: Compiling Nginx with BoringSSL results in an error

Hello, After testing, when compiling BoringSSL, on the test machine with GCC 12, you need to execute the command `sed -i 's/-Werror/-Werror -Wno-array-bounds/' CMakeLists.txt` for it to compile successfully. However, no issues were encountered during compilation with GCC 13. -- Best regard

Re: Issue with SSE and fcgiwrap in nginx (RESTCONF)

Hi Sergey, Thank you for the prompt reply! On Wed, May 14, 2025 at 2:31 AM Sergey A. Osokin wrote: > > [...] > > Is there a chance to build nginx with a debugging log as described on > the following page, https://nginx.org/en/docs/debugging_log.html > and tracing fcgi requests. Please expect a

Re: Compiling Nginx with BoringSSL results in an error

On Wed, May 14, 2025 at 05:45:42PM +0800, JINZE YANG via nginx wrote: > Hello, > Today, I pulled the latest branch from GitHub. Below > are the corresponding commits: > boringssl: 89973806bc2ef652189e157f2736a7d32229c404 > nginx: f3542500b6d74e3e88fc84b88144afe67882d1fa > Someone mentioned that thi

Re: Compiling Nginx with BoringSSL results in an error

Hello, Today, I pulled the latest branch from GitHub. Below are the corresponding commits: boringssl: 89973806bc2ef652189e157f2736a7d32229c404 nginx: f3542500b6d74e3e88fc84b88144afe67882d1fa Someone mentioned that this might be related to the GCC version. It seems GCC 13 does not have issues, but I

Re: Compiling Nginx with BoringSSL results in an error

Sorry, I used the wrong email format. I will be more careful next time. By the way, another person successfully compiled using GCC version 13 on Alpine. --- Best regards, JINZE YANG > 2025年5月14日 17:45，JINZE YANG 写道： > > Hello, > Today, I pulled the latest branch from GitHub. Below > are the

Re: Issue with SSE and fcgiwrap in nginx (RESTCONF)

Hi Rostyslav, hope you're doing well. Thanks for the report! On Tue, May 13, 2025 at 04:39:20PM -0700, Rostyslav Zalevskyy wrote: > Hello NGINX team, > > I'm working on a RESTCONF server that streams data via SSE. > > When using Apache2 with mod_fcgid, everything works fine: > multiple clients

Re: Compiling Nginx with BoringSSL results in an error

Hi there, hope you're doing well. Thanks for the report! On Wed, May 14, 2025 at 10:34:05AM +0800, 杨金泽 wrote: > It seems that BoringSSL has updated some of its interfaces, causing the > following issues during the compilation of Nginx. Is there currently any > solution to resolve this problem? Or

Re: Update nginx on the fly with a change of prefix

On Sun, May 04, 2025 at 11:24:39AM +0200, Sébastien Rebecchi wrote: > > Thank you for your answer. > When sending signal to the old master, doesn't it assume that the new > executable is located in the same location than the old one? Yes, it is. Thank you. -- Sergey A. Osokin __

Re: Update nginx on the fly with a change of prefix

Hi Sergey Thank you for your answer. When sending signal to the old master, doesn't it assume that the new executable is located in the same location than the old one? Sébastien. Le sam. 3 mai 2025, 18:32, Sergey A. Osokin a écrit : > Hi Sébastien, > hope you're doing well. > > On Sat, May 03,

Re: Update nginx on the fly with a change of prefix

Hi Sébastien, hope you're doing well. On Sat, May 03, 2025 at 06:14:19PM +0200, Sébastien Rebecchi via nginx wrote: > > Is there a way to update Nginx on the fly while new nginx was configured > with a different --prefix than was the old one? You may want following the "Upgrading Executable on t

Re: use a secondary upstream as backup

m: nginx on behalf of Sergey A. Osokin < > o...@freebsd.org.ru> > Sent: 23 April 2025 14:26 > To: Sébastien Rebecchi > Cc: nginx mailing list > Subject: Re: use a secondary upstream as backup > > CAUTION: This email has been sent from an external source. Do not click &

Re: use a secondary upstream as backup

; error_page 502 @try_secondary; } location @try_secondary { proxy_pass https://secondary_upstream; } From: nginx on behalf of Sergey A. Osokin Sent: 23 April 2025 14:26 To: Sébastien Rebecchi Cc: nginx mailing list Subject: Re: use a secondary

Re: use a secondary upstream as backup

Hi Sébastien, hope you're doing well. Thanks for the question. On Wed, Apr 23, 2025 at 12:07:21PM +0200, Sébastien Rebecchi via nginx wrote: > backup, meaning NGINX will only use them if all primary servers fail. > > In my case, I have some servers running over HTTP and would like to > configure

Re: Stable release date ?

Hi, The next mainline release (1.27.5) is planned this week. The next stable release (1.28.0) is planned next week. > On 14 Apr 2025, at 10:06 AM, Vishwas Bm wrote: > > Is this planned for release this week ? > > Thanks & Regards, > Vishwas > > On Tue, Mar 18, 2025, 11:28 Roman Arutyunyan

Re: Stable release date ?

Is this planned for release this week ? *Thanks & Regards,* *Vishwas* On Tue, Mar 18, 2025, 11:28 Roman Arutyunyan wrote: > Hello, > > Typically it's around April 12 each year. > > On 17 Mar 2025, at 3:42 PM, Vishwas Bm wrote: > > Hi, > > When is the next nginx stable release date ? > > I do n

Re: Stable release date ?

Hello, Typically it's around April 12 each year. > On 17 Mar 2025, at 3:42 PM, Vishwas Bm wrote: > > Hi, > > When is the next nginx stable release date ? > > I do not see it mentioned here > https://trac.nginx.org/nginx/roadmap > > > > Regards, > Vishwas >

Re: Is if statement valid for cert client verification ?

H, , ' ello. My my d xx xx xx be me z cc MC off to mm. Nx xx xx xx On Thu, Mar 13, 2025, 20:02 Mik J via nginx wrote: > Hello Thomas, > > Thank you for your answer and the time you took to write it down. > > Actually I had created a root CA and an Intermediate CA that I use to sign

Re: Is if statement valid for cert client verification ?

Hello Thomas, Thank you for your answer and the time you took to write it down. Actually I had created a root CA and an Intermediate CA that I use to sign my certificates. I am confused by the name of the directive "ssl_client_certificate" and in your explanation you tell me that I need to spec

Re: Is if statement valid for cert client verification ?

Hello Thomas, Thank you very much for these detailed explanations. I did use     ssl_client_certificate /etc/ssl/certs/myuser.crt;     ssl_verify_client on; But I had in mind to remove "ssl_client_certificate /etc/ssl/certs/myuser.crt", and replace it with if ($ssl_client_s_dn !~ "O=MyCorp") {

Re: Nginx ignores proxy_no_cache

s helps. > > We encounter disk failures fairly often and what the kernel will do most > of > > the time is re-mount the disk as read-only. > > What I did was add this check which checks if the disk is healthy before > > hand and executes the proxy_no_cache path if it is. &

Re: Nginx ignores proxy_no_cache

Hello! On Thu, Jan 30, 2025 at 11:01:32AM +0200, Clima Gabriel wrote: > Hello Maxim, > Hope this helps. > We encounter disk failures fairly often and what the kernel will do most of > the time is re-mount the disk as read-only. > What I did was add this check which checks if the

Re: Nginx ignores proxy_no_cache

Hello Maxim, Hope this helps. We encounter disk failures fairly often and what the kernel will do most of the time is re-mount the disk as read-only. What I did was add this check which checks if the disk is healthy before hand and executes the proxy_no_cache path if it is. It doesn't cove

Re: nginx with gitlab self host and cookie/session expired problems

"Nginx can't do much about it If the application behind deletes all the cookies." Yes, I am fully aware that this issue needs to be resolved at the application level, and we should apply the merge request as soon as possible. My final question about Nginx is more focused on the issue of session ex

RE: nginx with gitlab self host and cookie/session expired problems

> Now, I’m wondering if the frequent logouts (session expiration) might be > related to this cookie issue, and if there are any suggestions for addressing > it via Nginx. Nginx can't do much about it If the application behind deletes all the cookies. So check what version of Gitlab you are runni

Re: nginx and python script

Hi, On Fri, Dec 27, 2024 at 10:15:15PM +0100, Ralf Figge via nginx wrote: [...] > > i am a newbee from nginx. I need to run a python script via cgi-bin. That isn't nginx business to run cgi-bin scripts, but nginx can proxy a request to an application server behind. For the application server ro

Re: nginx and python script

Hi Jeff, /i am not shure, that this will be run ok. That was not the full line to call. I had think, that was only something to change in fcgiwrap. This was a part from a ZTP . Here the full python script, which run without changing under apache2 with mod_cgid. --

Re: nginx and python script

Pass {serial} to your proxy from a normal nginx args variable. location /another_script { proxy_pass http://server/cgi-bin/another_script.py? $args } And then you'll likely want to change from environ to the query string. I would also make

Re: WordPress Website not rendered properly via nginx reverse proxy

You could consider adding a CSP header to cause clients to automatically fetch those resources over HTTPS: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/upgrade-insecure-requests On Wed, 16 Oct 2024 at 00:06, Nikolaos Milas via nginx wrote: > On 16/10/2024 12

Re: WordPress Website not rendered properly via nginx reverse proxy

On 16/10/2024 12:19 π.μ., Nikolaos Milas via nginx wrote: ... I tried that but no, removing the trailing slash did not change anything. ... I found that the problem is that, as the proxied page is rendered over SSL, browsers are auto-blocking parts of the page as non-secure. This is due, I

Re: WordPress Website not rendered properly via nginx reverse proxy

On 15/10/2024 5:11 μ.μ., Kevin Weis via nginx wrote: have you tried to remove the trailing slash from the upstream url? Hi Kevin, Thanks for the hint. I tried that but no, removing the trailing slash did not change anything. Any other hints will be welcome! Thanks again, Nick smime.p7s

Re: NGINX has moved to Github!

agreements are you planning? Many of us use nginx only as a reverse proxy. It's fast and efficient. I flat out refuse to get into politics, but your announcement is not re-assuring. Do we need (fast? before year end?) a fall-back position? Thanks -- Paul Important: to report a securit

Re: Compilation of brotli for nginx fails since version 1.27.0 on Rocky Linux 8

Hi Nikolas, On Tue, Sep 03, 2024 at 10:48:30PM +0300, Nikolaos Milas via nginx wrote: > On 3/9/2024 9:57 μ.μ., Kevin Weis via nginx wrote: > > ... > > I was able to reproduce your exact error and find a solution that should > > meet your needs, using the current Rocky Linux 8 container image from

Re: Compilation of brotli for nginx fails since version 1.27.0 on Rocky Linux 8

On 3/9/2024 9:57 μ.μ., Kevin Weis via nginx wrote: ... I was able to reproduce your exact error and find a solution that should meet your needs, using the current Rocky Linux 8 container image from https://hub.docker.com/_/rockylinux with the image id of c79048e50f5f. My solution in short: I

Re: Default site configured for 444 returns 404

Improved 444 configuration: replaced the letsencrypt certificate (which won't work here anyway) with the self signed certificates bundled with nginx (the more broken, the merrier in this case... confuse the bots!): server { listen 80 default_server; listen [::]:80 default_server;

Re: Default site configured for 444 returns 404

Ok, found it! Turned out one of my other configs (the server www.mycompany.com one) had this server { # SSL configuration # listen 443 ssl default_server; listen [::]:443 ssl default_server; ssl_certificate /etc/letsencrypt/live/www.mycompany.com/fullch

Re: Default site configured for 444 returns 404

Found something! If I use https with the IP number and ignore the certificate errors caused by there being no certificate that matches the IP number, then I get a 200 OK (or presumably 404 as I've seen for some addresses). sb@marquez:~$ curl -svk https:/// * Trying :443... * Connected to () po

Re: Default site configured for 444 returns 404

> Jeffrey Walton : > The first two which succeed have a user agent string ("Expanse..." and > "Mozilla/5.0..."). The third one which fails lacks the user agent > string ("-"). > I'm not sure if that makes the difference in the behavior you are observing. > You may be able to test it with cUR

Re: Default site configured for 444 returns 404

On Sun, Aug 25, 2024 at 6:18 AM Steinar Bang wrote: > > > Steinar Bang : > > One piece of weirdness in the access.log. > > These two IP address requests for "/" returns 200. > > > 162.216.149.127 - - [23/Aug/2024:00:51:03 +] "" > > "GET / HTTP/1.1" 200 467 "-" "Expanse, a Palo Alto Networ

Re: Default site configured for 444 returns 404

> Steinar Bang : One piece of weirdness in the access.log. These two IP address requests for "/" returns 200. > 162.216.149.127 - - [23/Aug/2024:00:51:03 +] "" > "GET / HTTP/1.1" 200 467 "-" "Expanse, a Palo Alto Networks company, searches > across the global IPv4 space multipleer day

Re: Questions regarding upstream

Hi, On 09.08.24 22:16, Sébastien Rebecchi wrote: 1. When is it better to use random load-balancing strategy rather than the default round-robin one (and vice-versa)? Random selects always one randomly, while round robin usually sends the next request to the next server in the list. Persona

Re: Debugging CPU usage in Nginx

rotli to consume so much CPU power? From: nginx on behalf of Clima Gabriel Sent: Monday, August 12, 2024 11:32 PM To: nginx@nginx.org Subject: Re: Debugging CPU usage in Nginx If your Nginx is compiled with debug symbols you may see some useful info `perf top` On Mon, Aug 12,

Re: Debugging CPU usage in Nginx

If your Nginx is compiled with debug symbols you may see some useful info `perf top` On Mon, Aug 12, 2024, 6:24 PM Brad Patton wrote: > Hi all, > > About 2 months ago the CPU usage on 1 of our servers started going crazy. > All of a sudden, Nginx itself started using about 6x the CPU power to se

RE: nginx.org/packages: File has unexpected size (1244887 != 1246820)

SEO PCE) Objet : Re: nginx.org/packages: File has unexpected size (1244887 != 1246820) Hi Benjamin, Are you by any chance fetching the 1.27.0-1/1.26.1-1 versions of the packages and their corresponding sources? Indeed, we had a bit of a mishap when publishing them leading to the errors you&#x

Re: nginx.org/packages: File has unexpected size (1244887 != 1246820)

Hi Benjamin, Are you by any chance fetching the 1.27.0-1/1.26.1-1 versions of the packages and their corresponding sources? Indeed, we had a bit of a mishap when publishing them leading to the errors you're seeing: ubuntu22:~/src$ apt-get source nginx=1.27.0-1~jammy Reading package lists...

Re: nginx.org/packages: File has unexpected size (1244887 != 1246820)

I wouldn't trust a build if the hash doesn't match. I'd use the version before it which does match. Was there an issue with the earlier version? On Mon, Aug 12, 2024, 3:21 AM FERRON, BENJAMIN via nginx wrote: > Hi, > > > > I’ve been experiencing issues fetching the sources of nginx 1.27.0 (deb

Re: nginx/1.26.1 as a reverse proxy strips the Content-Length field from response, no matter what I do

I am awfully sorry for spamming this list. I just found out nextcloud starts sending the file several times, sometimes containing "Content-Length" and sometimes not. The one time it actually serves the full download, this is the header: ---

Re: [ANN] OpenResty 1.25.3.2 released

We have fully understood the cause of the problem. The reason for disabling rather than reverting the entire commit is because we want to continue to use SSE to speed things up in the future. On Mon, Jul 22, 2024 at 4:10 PM Mathew Heard wrote: > Now that there is a patch out could you please sha

Re: [ANN] OpenResty 1.25.3.2 released

Now that there is a patch out could you please share more information on those "specific circumstances"? It looks to me that luajit2 does not support SSE4.2 whereas agentzh's fork does. And this is what has been disabled in this release. Is this an interim release while the cause is investigated o

Re: [ANN] OpenResty 1.25.3.2 released

Is there any ETA for new docker builds of openresty for this as well? Sent from Outlook for iOS From: nginx on behalf of Jiahao Wang via nginx Sent: Monday, July 22, 2024 9:45:44 AM To: nginx@nginx.org Cc: Jiahao Wang Subject: [ANN] Open

Re: Upgrading Executable on the Fly

Hello I understand that sending signals is async so there is no guarantee that QUIT is not processed before USR2 so nginx receiving QUIT will ignore USR2 if received after QUIT. I think of a faster solution still being safe kill -USR2 $nginxPid *ADDED: wait until nginx pid file has a content diff

Re: Bugfix: graceful shutdown of old worker processes might be delayed when using HTTP/2.

Thanks Roman! Le jeu. 18 juil. 2024 à 15:53, Roman Arutyunyan a écrit : > Hello, > > On 11 Jul 2024, at 1:12 PM, Roman Arutyunyan wrote: > > Hi Sébastien, > > On 9 Jul 2024, at 5:52 PM, Sébastien Rebecchi > wrote: > > Hi! > > We are using nginx a lot in our company for high HTTP/2 workloads. >

Re: Bugfix: graceful shutdown of old worker processes might be delayed when using HTTP/2.

Hello, > On 11 Jul 2024, at 1:12 PM, Roman Arutyunyan wrote: > > Hi Sébastien, > >> On 9 Jul 2024, at 5:52 PM, Sébastien Rebecchi >> wrote: >> >> Hi! >> >> We are using nginx a lot in our company for high HTTP/2 workloads. >> >> I saw freenginx has applied a bugfix in their last mainline r

Re: nginx pgp key nginx_signing.key

Hi Ivan! On 07/07/2024 6:39 AM, Ivan Strelnikov via nginx wrote: Hello! Many years ago i started use `nginx_signing.key` from this url: `https://nginx.org/packages/keys/nginx_signing.key` but now i find out that it is expired and outdated. Fresh key is here: `https://nginx.org/keys/nginx_si

Re: Bugfix: graceful shutdown of old worker processes might be delayed when using HTTP/2.

Thanks Roman, I am expecting that :) Le jeu. 11 juil. 2024 à 11:12, Roman Arutyunyan a écrit : > Hi Sébastien, > > On 9 Jul 2024, at 5:52 PM, Sébastien Rebecchi > wrote: > > Hi! > > We are using nginx a lot in our company for high HTTP/2 workloads. > > I saw freenginx has applied a bugfix in th

Re: Bugfix: graceful shutdown of old worker processes might be delayed when using HTTP/2.

Hi Sébastien, > On 9 Jul 2024, at 5:52 PM, Sébastien Rebecchi wrote: > > Hi! > > We are using nginx a lot in our company for high HTTP/2 workloads. > > I saw freenginx has applied a bugfix in their last mainline release 1.27.1, > see https://freenginx.org/en/CHANGES > *) Bugfix: graceful

Re: proxy_bind/splitting with nginx mail module for IMAP

Hi Malte, hope you're doing well. On Wed, Jul 10, 2024 at 07:09:42PM +0200, Malte Schmidt via nginx wrote: > > I am currently working on a setup using nginx mail module with several > backends. Due to port exhaustion, I would like to do splitting of outgoing > connections across several IPs. For

Re: Enable http3 for a subset of domains

Hi, > On 27 Jun 2024, at 10:17 AM, Riccardo Brunetti Host > wrote: > > > >> On 26 Jun 2024, at 17:56, Roman Arutyunyan > > wrote: >> >> Hi, >> >>> On 26 Jun 2024, at 7:21 PM, Riccardo Brunetti Host >>> mailto:riccardo.brune...@host.it>> wrote: >>> >>> Hello, thanks

Re: Enable http3 for a subset of domains

> On 26 Jun 2024, at 17:56, Roman Arutyunyan wrote: > > Hi, > >> On 26 Jun 2024, at 7:21 PM, Riccardo Brunetti Host >> wrote: >> >> Hello, thanks for the answer. >> >>> On 26 Jun 2024, at 16:45, Roman Arutyunyan >> > wrote: >>> >>> Hi, >>> On 26 Jun 2024, at 6

Re: Enable http3 for a subset of domains

Hi, > On 26 Jun 2024, at 7:21 PM, Riccardo Brunetti Host > wrote: > > Hello, thanks for the answer. > >> On 26 Jun 2024, at 16:45, Roman Arutyunyan > > wrote: >> >> Hi, >> >>> On 26 Jun 2024, at 6:15 PM, Riccardo Brunetti Host >>> mailto:riccardo.brune...@host.it>> wr

Re: Enable http3 for a subset of domains

Hello, thanks for the answer. > On 26 Jun 2024, at 16:45, Roman Arutyunyan wrote: > > Hi, > >> On 26 Jun 2024, at 6:15 PM, Riccardo Brunetti Host >> wrote: >> >> Hello. >> >> I have a Nginx server which acts as a reverse proxy for a given number of >> different domains and I’m trying to en

Re: Enable http3 for a subset of domains

Hi, > On 26 Jun 2024, at 6:15 PM, Riccardo Brunetti Host > wrote: > > Hello. > > I have a Nginx server which acts as a reverse proxy for a given number of > different domains and I’m trying to enable http3 for a subset of them. > > I placed the directives: > >> http3 on; >> listen x

Re: How important is the "reuseport" flag for quic?

On Tue, 25 Jun 2024 at 16:35, J Carter wrote: > Very, it's required to use the reuseport parameter when using multiple > workers as per the documentation here[1] so that all UDP packets of a > HTTP/3/quic connection are routed to and handled by the same worker, as > I understand. I see, thanks.

Re: How important is the "reuseport" flag for quic?

he browser > ultimately falls back to http/2. > > When I re-add "reuseport", all http/3 requests succeed again. > > How crucial is "reuseport" when using quic on nginx? Is it normal for > things to break badly without it? >

Re: Allow response with AD bit in resolver

Greetings, On Mon, 17 Jun 2024 19:08:22 +0100, J Carter wrote: > > It's caused by DNS Cache poisoning (either intentionally, or > unintentionally), from a recursive resolver that caches CD bit but > does not zero it if a non dns-sec query hits that cached response. > > I see unbound also has a

Re: Allow response with AD bit in resolver

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 client in quite a simplistic fashion,

Re: Allow response with AD bit in resolver

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 client in quite a simplistic fashion, and nginx > does not support DNSSEC, it makes little sense to hyper-strict about > t

Re: Allow response with AD bit in resolver

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 > > Unfortunately, the AD bit is set b

Re: Allow response with AD bit in resolver

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 Unfortunately, the AD bit is set by the libunbound-based resolver when it is configured to use an upstream forwarder that

Re: Allow response with AD bit in resolver

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 >

Re: Custom HTTP protocol response?

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 ngx_http_header_f

Re: Allow response with AD bit in resolver

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 > --- src/core/ngx_resolver.c.orig > +++ src/core/ngx_resolver.c > @@ -1774,7

Re: Custom HTTP protocol response?

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 ngx_http_header_filter_module.c such string is hardcoded. -- wbr, Kirill ___

Re: nginx-1.27.0 - shasum does not match with expected shasum from pkg-oss

On 29/05/2024 17:22, Igor Ippolitov wrote: On 29/05/2024 16:52, Daniel Jagszent wrote: Hello, the SHA512 of https://nginx.org/download/nginx-1.27.0.tar.gz (downloaded 2024-05-29 15:42:02 UTC) is 251bfe65c717a8027ef05caae2ab2ea73b9b544577f539a1d419fe6adf0bcc846b73b58f54ea3f102df79aaf340e4fa56793

Re: nginx-1.27.0 - shasum does not match with expected shasum from pkg-oss

On 29/05/2024 16:52, Daniel Jagszent wrote: Hello, the SHA512 of https://nginx.org/download/nginx-1.27.0.tar.gz (downloaded 2024-05-29 15:42:02 UTC) is 251bfe65c717a8027ef05caae2ab2ea73b9b544577f539a1d419fe6adf0bcc846b73b58f54ea3f102df79aaf340e4fa56793ddadea3cd61bcbbe2364ef94bacb This does not

Re: NGINX multiple authentication methods (one or the other) AND an IP check seems impossible

That works wonderfully, thank you! On May 27, 2024 6:48:40 AM UTC, J Carter wrote: >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

Re: NGINX multiple authentication methods (one or the other) AND an IP check seems impossible

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 Just

Re: Twitter incompatibility

Fixed, many thanks. I had asked ChatGPT 4o and it could not help. On Sun, May 19, 2024 at 6:28 PM J Carter wrote: > > 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 thi

Re: Twitter incompatibility

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 > https://xlong.org/p/a36

Re: nginx configured as loadbalancer returning 404 not found

On Fri, May 17, 2024 at 7:39 PM Sergey A. Osokin wrote: > Hi Kaushal, > > On Fri, May 17, 2024 at 04:49:59PM +0530, Kaushal Shriyan wrote: > > > > I am running nginx version 1.26 on "Ubuntu 22.04.4 LTS" I have configured > > the nginx as load balancer and the configuration details are as follows

Re: nginx configured as loadbalancer returning 404 not found

Hi Kaushal, On Fri, May 17, 2024 at 04:49:59PM +0530, Kaushal Shriyan wrote: > > I am running nginx version 1.26 on "Ubuntu 22.04.4 LTS" I have configured > the nginx as load balancer and the configuration details are as follows > > # nginx -v > nginx version: nginx/1.26.0 > # > > server { [...

Re: Status code 0

Hello Just to close that conversation, it seems this was an error of our devops in charge of alerting, who was using curl in a bad way. Best regards, Sébastien Le lun. 6 mai 2024 à 11:33, Sébastien Rebecchi a écrit : > Hello! > > There is nothing regarding this issue in nginx logs. > > Now I

Re: Bypass cache if PHPSESSID exists

On Thu, 09 May 2024 18:11:18 +0100, Christos Chatzaras wrote: > > if ($http_cookie ~* "_mcnc|PHPSESSID") { > set $no_cache "1"; > } > Try to use map instead if. -- wbr, Kirill ___ nginx mailing list n

Re: Status code 0

Hello! There is nothing regarding this issue in nginx logs. Now I think the issue is not with nginx itself, but in front of nginx, with Linux itself. We monitor using curl, and it seems that curl can print status code 0 when it can not establish a connection with the server. I think the Linux ker

Re: Status code 0

Hello! On Sat, May 04, 2024 at 07:31:43PM +0200, Sébastien Rebecchi wrote: > Hello > > What does it mean when nginx returns an http status code 0? > > We see that cause we monitor nginx response status code, which is used as > front of our apps. The apps themselves can not return 0, only 200 or

Re: Status code 0

Hi Sébastien, thanks for the report. On Sat, May 04, 2024 at 07:31:43PM +0200, Sébastien Rebecchi wrote: > > What does it mean when nginx returns an http status code 0? > > We see that cause we monitor nginx response status code, which is used as > front of our apps. The apps themselves can not

  1   2   3   4   5   6   7   8   9   10   >