slice module not handling 416

i'm trying to use the slice module to cache large files, as described here: https://guo365.github.io/study/nginx.org/en/docs/admin-guide/Web%20content%20cache.html#slice however, the slice module _always_ requests the full slice range regardless of the size of the file, and the servers that i'm

Re: no TLS1.3 with 1.15.5

Hello! On Sat, Nov 03, 2018 at 06:14:15PM +, Bogdan via nginx wrote: > Hello, everyone. > > I am stuck with a fresh installation which runs absolutely fine except it > doesn't offer TLS1.3 which is the the biggest reason for updating the server. > > Below is some info about my config. > >

Re: Using URL instead of IP

Hello! On Tue, Nov 06, 2018 at 12:44:47AM -0500, swati wrote: > Hi, > > I intend to use nginx as load balancer for routing traffic to an application > running on two separate Openshift (kubernetes) clusters. > The app urls are -> app.dc1.example.com and app.dc2.example.com. > When I curl to thes

Re: [nginx-announce] nginx-1.15.6

Hello Nginx users, Now available: Nginx 1.15.6 for Windows https://kevinworthington.com/nginxwin1156 (32-bit and 64-bit versions) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at nginx.org. Announc

Re: [nginx-announce] nginx-1.14.1

Hello Nginx users, Now available: Nginx 1.14.1 for Windows https://kevinworthington.com/nginxwin1141 (32-bit and 64-bit versions) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at nginx.org. Announc

nginx security advisory (CVE-2018-16845)

Hello! A security issue was identified in the ngx_http_mp4_module, which might allow an attacker to cause infinite loop in a worker process, cause a worker process crash, or might result in worker process memory disclosure by using a specially crafted mp4 file (CVE-2018-16845). The issue only aff

nginx security advisory (CVE-2018-16843, CVE-2018-16844)

Hello! Two security issues were identified in nginx HTTP/2 implementation, which might cause excessive memory consumption (CVE-2018-16843) and CPU usage (CVE-2018-16844). The issues affect nginx compiled with the ngx_http_v2_module (not compiled by default) if the "http2" option of the "listen" d

nginx-1.14.1

Changes with nginx 1.14.106 Nov 2018 *) Security: when using HTTP/2 a client might cause excessive memory consumption (CVE-2018-16843) and CPU usage (CVE-2018-16844). *) Security: processing of a specially crafted mp4 file with the ngx

nginx-1.15.6

Changes with nginx 1.15.606 Nov 2018 *) Security: when using HTTP/2 a client might cause excessive memory consumption (CVE-2018-16843) and CPU usage (CVE-2018-16844). *) Security: processing of a specially crafted mp4 file with the ngx

Re: SSLEngine closed already exception triggered by reload

One setting that I noticed mitigates the problem is to use `lingering_close always;` however in our infrastructure this can lead to the build up of worker processes (for the duration of the lingering_timeout). What are the advantages and drawbacks of using this setting? Posted at Nginx Forum: ht

Re: How to use dynamic IP in resolver directive when NGINX installed on Multi Nodes Openshift cluster

Hi Marwan, Did you find solution for this one? Can you please share your configurations? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,281239,281791#msg-281791 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listin