[njs] Tests: improved memory sanitizer build.

2023-06-30 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/3386684745b7 branches: changeset: 2174:3386684745b7 user: Dmitry Volyntsev date: Fri Jun 30 21:02:44 2023 -0700 description: Tests: improved memory sanitizer build. Disable webcrypto tests because they required instrumented openssl. diffstat:

[njs] Improved interactive shell.

2023-06-30 Thread Vadim Zhestikov via nginx-devel
details: https://hg.nginx.org/njs/rev/0e97da4147da branches: changeset: 2173:0e97da4147da user: Vadim Zhestikov date: Fri Jun 30 19:49:46 2023 -0700 description: Improved interactive shell. diffstat: external/njs_shell.c | 17 - 1 files changed, 12 insertions(+),

[njs] Fixed parsing of invalid for statement.

2023-06-30 Thread Vadim Zhestikov via nginx-devel
details: https://hg.nginx.org/njs/rev/2c532e7c29ac branches: changeset: 2172:2c532e7c29ac user: Vadim Zhestikov date: Fri Jun 30 19:49:45 2023 -0700 description: Fixed parsing of invalid for statement. diffstat: src/njs_parser.c | 16 ++--

Re: Possible bug with "proxy_intercept_errors on; " + "error_page 301 302"?

2023-06-30 Thread Fabiano Furtado Pessoa Coelho
Thanks. On Fri, Jun 30, 2023, 9:44 PM Maxim Dounin wrote: > Hello! > > On Fri, Jun 30, 2023 at 01:24:18PM -0300, Fabiano Furtado Pessoa Coelho > wrote: > > > Hello Maxim... > > > > On Thu, Jun 29, 2023 at 7:00 PM Maxim Dounin wrote: > > > > > > Hello! > > > > > > On Thu, Jun 29, 2023 at

[PATCH 2 of 2] Tests: adjusted TODO for OpenSSL 1.0.2h and up in h2_http2.t

2023-06-30 Thread Maxim Dounin
# HG changeset patch # User Maxim Dounin # Date 1688164312 -10800 # Sat Jul 01 01:31:52 2023 +0300 # Node ID 5ef10e454094ad5d231552f0fc2c386e9cc33585 # Parent bf9961a4507784b669650e7ef1d3cbacce8c94e1 Tests: adjusted TODO for OpenSSL 1.0.2h and up in h2_http2.t. OpenSSL uses correct

[PATCH 1 of 2] Tests: fixed h2_http2.t when nginx compiled without ALPN support

2023-06-30 Thread Maxim Dounin
# HG changeset patch # User Maxim Dounin # Date 1688164311 -10800 # Sat Jul 01 01:31:51 2023 +0300 # Node ID bf9961a4507784b669650e7ef1d3cbacce8c94e1 # Parent 22f45bf99a9e39e02d8ce07532d2cbfc89e7d8d1 Tests: fixed h2_http2.t when nginx compiled without ALPN support. ALPN support is only

[PATCH 0 of 2] h2_http2.t fixes

2023-06-30 Thread Maxim Dounin
Hello! Here is a couple of fixes for h2_http2.t to make it work with various old OpenSSL versions. -- Maxim Dounin ___ nginx-devel mailing list nginx-devel@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-devel

Re: Possible bug with "proxy_intercept_errors on; " + "error_page 301 302"?

2023-06-30 Thread Maxim Dounin
Hello! On Fri, Jun 30, 2023 at 01:24:18PM -0300, Fabiano Furtado Pessoa Coelho wrote: > Hello Maxim... > > On Thu, Jun 29, 2023 at 7:00 PM Maxim Dounin wrote: > > > > Hello! > > > > On Thu, Jun 29, 2023 at 04:29:39PM -0300, Fabiano Furtado Pessoa Coelho > > wrote: > > > > > Hi... > ... > > >

[njs] Tests: fixed benchmark after 57ca02d7404c.

2023-06-30 Thread Dmitry Volyntsev
details: https://hg.nginx.org/njs/rev/494796d6d7f8 branches: changeset: 2171:494796d6d7f8 user: Dmitry Volyntsev date: Fri Jun 30 17:03:11 2023 -0700 description: Tests: fixed benchmark after 57ca02d7404c. diffstat: src/test/njs_benchmark.c | 15 +-- 1 files changed,

Re: Documentation of Nginx configuration file directives

2023-06-30 Thread Maxim Konovalov
Hi Sam, On 30.06.2023 12:46, Sam Hobbs wrote: Is there official documentation of the nginx configuration file directives? I find many articles describing nginx configuration files but they do not describe all of the directives, certainly not like official documentation typically does. The

Documentation of Nginx configuration file directives

2023-06-30 Thread Sam Hobbs
Is there official documentation of the nginx configuration file directives? I find many articles describing nginx configuration files but they do not describe all of the directives, certainly not like official documentation typically does. ___ nginx

Re: Possible bug with "proxy_intercept_errors on; " + "error_page 301 302"?

2023-06-30 Thread Fabiano Furtado Pessoa Coelho
Hello Maxim... On Thu, Jun 29, 2023 at 7:00 PM Maxim Dounin wrote: > > Hello! > > On Thu, Jun 29, 2023 at 04:29:39PM -0300, Fabiano Furtado Pessoa Coelho wrote: > > > Hi... ... > > "proxy_intercept_errors on;"? > > The "proxy_intercept_errors" handling does not copy any response > headers from

Re: Accessing electronic resources from outside the corporate network: Proxy or VPN?

2023-06-30 Thread Mauro Tridici
Thank you for you reply, Thomas. My boss also pointed me to the name of EZproxy. But I'm with you and with your suggestion. Do you know of any forums or communities, dedicated to security, from which you can extract information regarding the pros and cons of using proxies or VPN? Mauro > On

RE: Accessing electronic resources from outside the corporate network: Proxy or VPN?

2023-06-30 Thread Thomas Ward
I would not consider NGINX a proxy in the form you're looking for - it's not designed to work as a "proxy" server in the sense of what you're looking for, and VPN + internal proxy is the better solution for access to resources subscribed to a company (but that's outside the scope of NGINX and

Accessing electronic resources from outside the corporate network: Proxy or VPN?

2023-06-30 Thread Mauro Tridici
Dear Users, my boss asked me to implemented a proxy service in order to allow corporate users to access electronic resources, subscribed by our company, also from outside the corporate network (you know, users can work both from office and from home). Unfortunately, I’m a newbie and I’m a

[njs] Added constructor name for async function.

2023-06-30 Thread Vadim Zhestikov via nginx-devel
details: https://hg.nginx.org/njs/rev/e85aaeaa7e55 branches: changeset: 2170:e85aaeaa7e55 user: Vadim Zhestikov date: Fri Jun 30 06:38:36 2023 -0700 description: Added constructor name for async function. diffstat: src/njs_async.c | 2 ++ 1 files changed, 2 insertions(+), 0

Mixing limit_except breaks rewrite functionality: workaround request

2023-06-30 Thread Sten Gruener
Dear all, I trying to mix authentication for POST requests with some rewrite/proxy_pass logic. This mean that password is required only on POST/PUT requests. location /x/ { limit_except GET OPTIONS { auth_basic "Write Access";