Re: Automatic trailing slash redirect and scheme

On Thu, Aug 22, 2019 at 03:22:38PM +0200, Jean-Daniel FISCHER wrote: Hi there, > I an trying to set the sheme used in automatic redirect generates by nginx > when trailing slash is missing. The nginx server is behind a proxy that > handles ssl, hence all requests are made using http so nginx use

Unit 1.10.0 release

Hi, I'm glad to announce a new release of NGINX Unit. This release includes a number of improvements in various language modules and, finally, basic handling of incoming WebSocket connections, currently only for Node.js. Next in line to obtain WebSocket support is the Java module; it's almost re

Re: Is there a limitation in nginx on the number of simultaneous via proxy_pass

If do index.html and nginx.conf like below, that displays all index.html - ... nginx.conf --- location /aaa/ { rewrite ^/aaa/ http://mysite.org:9000";; } ... Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285362,285377#msg-285

Re: RE: Setting a custom header based on another upstream/sent header

Thank you Reinis - that did it :) Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285363,285374#msg-285374 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Nginx + Lua Anti-DDoS Script Authentication page like Cloudflare Bitmitigate sucuri etc

So i thought i would share this here to get some feedback help bring to light some improvements and bugs and to get the ball rolling on how we can make this script better :) I made this because I like the way Cloudflare, BitMitigate and such sites protect their backends with a HTML, Javascript aut

Re: Automatic trailing slash redirect and scheme

Hello, You can try adding an 'error_page 301 @returnme' and then a location like this: location @returnme {     return 301 https://$host$uri/$is_args$args; } Regards, Igor On 22.08.2019 16:22, Jean-Daniel FISCHER wrote: Hi, I an trying to set the sheme used in automatic redirect generates b

Re: Is there a limitation in nginx on the number of simultaneous via proxy_pass

No, it’s browser limitation -- Hưng > On Aug 22, 2019, at 18:44, glareboa wrote: > > Is there a limitation in nginx on the number of simultaneous via proxy_pass > "http://192.168.1.2:90xx";? > > From the source http://192.168.1.2:90xx MJPEG is transmitted. Speed 200 > kB/sec. > > The browser

Re: Nginx agent grpc error  

> On 22 Aug 2019, at 15:05, aiaa5505 wrote: > > [error] 8#8: *256283 upstream rejected request with error 0 while reading > response header from upstream, HTTP/2.0 > It is not something nginx gRPC proxy currently supports. See https://trac.nginx.org/nginx/ticket/1792 for details and proposed

Automatic trailing slash redirect and scheme

Hi, I an trying to set the sheme used in automatic redirect generates by nginx when trailing slash is missing. The nginx server is behind a proxy that handles ssl, hence all requests are made using http so nginx use http in absolute redirect. Is there a way to configure nginx to use the value of

Re: nginx-1.16.1

Hello, Can you please comment on the question? Or at least say that there are no guarantees of safety in applying the patches on the nginx-1.14.2 branch? Thanks. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285234,285366#msg-285366 ___ n

RE: Setting a custom header based on another upstream/sent header

> Is this expected behaviour? Could there be another way to do this? 'if' (the rewrite module) is executed in early stages when $sent_* variables are not available that’s why the regex doesn't match. What you could do is use 'map' instead: (http://nginx.org/en/docs/http/ngx_http_map_module.html

Nginx agent grpc error  

[error] 8#8: *256283 upstream rejected request with error 0 while reading response header from upstream, HTTP/2.0 I encountered such an error during the process of using nginx The version I am using is 1.17.3 docker image   Posted at Nginx Forum: https://forum.nginx.org/read.php?2,285364,285

Setting a custom header based on another upstream/sent header

Hi there, I'm trying (unsuccessfully) to read an upstream/sent response header and set an additional one based on some regex. Let's say I want to check if the site served is WordPress. WordPress will usually output a link header like this: link: ; rel="https://api

Is there a limitation in nginx on the number of simultaneous via proxy_pass

Is there a limitation in nginx on the number of simultaneous via proxy_pass "http://192.168.1.2:90xx";? >From the source http://192.168.1.2:90xx MJPEG is transmitted. Speed 200 kB/sec. The browser displays only 6 video streams (id=1 ... id=6). Threads id=7 ... id=9 not visible. index.html --