Re: Nginx cache-control headers issue

I tried with upstream cache control and this is the results: Request URL: https://example.com/hls/nickelback/Nickelback-Lullaby_1280_720_1300011.ts?token=st=1563586913~exp=1563673313~acl=/hls/nickelback/*~hmac=bad8f13314c29ec41312b6f10b9106a2f1f024fdfbfce090d9a08bd0a635928f 1.

Re: cache: move open to thread pool

> The patch wasn't updated since that but I suspect it could be still applied to nginx, maybe with some minor tweaks. We still appreciate your work. BTW, are the patches in the attachment up to date? If not, can you share the latest patch? We are happy to apply it and feedback if possible. When

Re: Nginx cache-control headers issue

Hi Francis, Thanks for the response, I checked multiple scenarios and when I removed the token I got the correct header. Looks like when the token is active, I am getting wrong headers. Also "upstream" you mean the Origin for nginx? which is in my case is S3 For example, this is a token-based

Re: Nginx cache-control headers issue

On Thu, Jul 18, 2019 at 06:44:13PM -0400, andregr-jp wrote: Hi there, > I have an nginx proxy which suddenly adding 2 cache-control headers and the > last modified time is always the current time: I suspect that whatever is being reverse-proxied changed recently to send these headers. >

[njs] Added Object shorthand methods and computed property names.

details: https://hg.nginx.org/njs/rev/97ab91a7c7f5 branches: changeset: 1064:97ab91a7c7f5 user: hongzhidao date: Tue Jul 02 22:24:11 2019 -0400 description: Added Object shorthand methods and computed property names. This closes #182 issue on Github. diffstat: njs/njs_parser.c

Avoid creating a temp file on Nginx host

I'm using Nginx in proxy pass mode to serve an application. We have had some issues where the host running Nginx doesn't have enough space to host some uploaded files. Is there a way to stream this files to the backend server without creating a temporary file in the Nginx host? Based on the post

Re: How to configure Nginx LB IP-Transparency for custom UDP application

Am 16.07.2019 um 13:29 schrieb Jeya Murugan: > @all : Can someone help /point-out what i have missed in > proxy_protocol > here?  the proxy protocol is only designed for tcp not udp. > > I am using *NGINX 1.13.5 as a Load Balancer for one of my > >

[njs] Inlining call to hash function in njs_property_query().

details: https://hg.nginx.org/njs/rev/9da8ebc3dc07 branches: changeset: 1063:9da8ebc3dc07 user: Dmitry Volyntsev date: Fri Jul 19 23:27:53 2019 +0300 description: Inlining call to hash function in njs_property_query(). diffstat: njs/njs_object_property.c | 5 + 1 files

[njs] Refactored working with non-primitive types.

details: https://hg.nginx.org/njs/rev/201af81dfa9b branches: changeset: 1060:201af81dfa9b user: Dmitry Volyntsev date: Fri Jul 05 21:45:28 2019 +0300 description: Refactored working with non-primitive types. Traps mechanism is remove. diffstat: njs/njs.c |

[njs] Added njs_set_int32() and njs_set_uint32() intrinsics.

details: https://hg.nginx.org/njs/rev/8b977c78885f branches: changeset: 1062:8b977c78885f user: Dmitry Volyntsev date: Fri Jul 19 22:05:34 2019 +0300 description: Added njs_set_int32() and njs_set_uint32() intrinsics. diffstat: njs/njs_value.h | 18 ++

[njs] Refactored working with function calls.

details: https://hg.nginx.org/njs/rev/540f03725df2 branches: changeset: 1061:540f03725df2 user: hongzhidao date: Tue Jul 16 22:44:16 2019 -0400 description: Refactored working with function calls. 1) njs_continuation_t is removed (appropriate functions are rewritten).

Re: How to configure Nginx LB IP-Transparency for custom UDP application

On Fri, Jul 12, 2019 at 11:44:22PM +0530, Jeya Murugan wrote: > On Tue, Jul 9, 2019 at 8:41 PM Roman Arutyunyan wrote: Hi there, > > > I am using *NGINX 1.13.5 as a Load Balancer for one of my > > > CUSTOM-APPLICATION *which will listen on* UDP port 2231,67 and 68.* > > > > > > I am trying for

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

You may want to re-read my initial answer and the ticket it links to. If that were _clear_, neither I nor others would STILL be spending time/effort trying to understand & clarify this. Nevermind. ___ nginx mailing list nginx@nginx.org

Re: cache: move open to thread pool

Hi hongzhidao, The patch wasn't merged as we didn't see much interest and real technical feedback from potential testers. The code adds additional complexity to the nginx core with all associated costs of maintaining the code virtually forever. In the same time at this point it brings no

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

Hello! On Fri, Jul 19, 2019 at 11:24:36AM -0700, PGNet Dev wrote: > On 7/19/19 11:02 AM, Maxim Dounin wrote: > > Hello! > > > > On Fri, Jul 19, 2019 at 10:52:55AM -0700, PGNet Dev wrote: > > > And, if I change nginx to be 'TLSv1.3-only', > > -ssl_protocols TLSv1.3

Re: SSL_write() failed errors

> On 19 Jul 2019, at 9.59, Maxim Dounin wrote: > > Hello! > > On Thu, Jul 18, 2019 at 10:03:24AM -0700, Palvelin Postmaster via nginx wrote: > >> we’re getting random SSL_write() failed errors on seemingly >> legitimate requests. The common denominator seems to be they are >> all for

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

On 7/19/19 11:02 AM, Maxim Dounin wrote: > Hello! > > On Fri, Jul 19, 2019 at 10:52:55AM -0700, PGNet Dev wrote: > And, if I change nginx to be 'TLSv1.3-only', - ssl_protocols TLSv1.3 TLSv1.2; - ssl_ciphers "TLS13-CHACHA20-POLY1305-SHA256 TLS13-AES-256-GCM-SHA384

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

Hello! On Fri, Jul 19, 2019 at 10:52:55AM -0700, PGNet Dev wrote: > >> And, if I change nginx to be 'TLSv1.3-only', > >> > >> - ssl_protocols TLSv1.3 TLSv1.2; > >> - ssl_ciphers "TLS13-CHACHA20-POLY1305-SHA256 TLS13-AES-256-GCM-SHA384 > >> TLS13-AES-128-GCM-SHA256

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

>> And, if I change nginx to be 'TLSv1.3-only', >> >> -ssl_protocols TLSv1.3 TLSv1.2; >> -ssl_ciphers "TLS13-CHACHA20-POLY1305-SHA256 TLS13-AES-256-GCM-SHA384 >> TLS13-AES-128-GCM-SHA256 ECDHE-ECDSA-CHACHA20-POLY1305"; >> +ssl_protocols TLSv1.3; >> +ssl_ciphers

Re: SSL_write() failed errors

Hello! On Thu, Jul 18, 2019 at 10:03:24AM -0700, Palvelin Postmaster via nginx wrote: > we’re getting random SSL_write() failed errors on seemingly > legitimate requests. The common denominator seems to be they are > all for static files (images, js, etc.). > > Can anyone help me debug the

Re: nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

Hello! On Fri, Jul 19, 2019 at 08:39:15AM -0700, PGNet Dev wrote: > I run nginx > > nginx -v > nginx version: nginx/1.17.1 > > on linux/64. > > I've installed > > which openssl > /usr/local/openssl/bin/openssl > openssl version >

Autoindex, "no mapping" и русские имена файлов под Windows

Всем привет, у меня встала задача расшарить большой каталог под Windows "в Интернет" с помощью nginx. Autoindex on прекрасно справился с этой задачей, но только что касается английских имен файлов. Русские имена nginx показывает корректно, но при попытке перейти в русский каталог или скачать

Re: TLS1.3

On 7/19/19 12:09 PM, Maxim Dounin wrote: > Hello! > > On Thu, Jul 18, 2019 at 04:01:39PM -0400, Thomas Ward wrote: > >> Downstream, in Ubuntu, we've got NGINX 1.14.0 in the repositories, and >> TLS 1.3 enabled in the bionic-updates repository due to OpenSSL being >> bumped to 1.1.1.  We don't

[njs] Fixed njs_string_slice().

details: https://hg.nginx.org/njs/rev/2fdad3cbbd74 branches: changeset: 1059:2fdad3cbbd74 user: Dmitry Volyntsev date: Thu Jul 18 21:12:25 2019 +0300 description: Fixed njs_string_slice(). Previously, njs_string_slice() when slice->start == slice->string_length may call

nginx 1.17.1 configcheck fails if config'd for TLSv1.3-only ?

I run nginx nginx -v nginx version: nginx/1.17.1 on linux/64. I've installed which openssl /usr/local/openssl/bin/openssl openssl version OpenSSL 1.1.1c 28 May 2019 nginx is built with/linked to this version ldd

[nginx] Core: fixed memory leak on error, missed in c3f60d618c17.

details: https://hg.nginx.org/nginx/rev/eb9c7fb796d5 branches: changeset: 7541:eb9c7fb796d5 user: Maxim Dounin date: Fri Jul 19 17:50:00 2019 +0300 description: Core: fixed memory leak on error, missed in c3f60d618c17. Found by Coverity (CID 1451664). diffstat: