On Tue, 7 Jun 2022 at 14:15, Sergey Kandaurov <pluknet@nginx.com> wrote: > > On 7 Jun 2022, at 13:41, Peter Volkov <peter.volkov@gmail.com> wrote: > > After we enabled HTTP/2 in nginx some old software started to fail. So > we would like to have HTTP v2 enabled in general but disabled for some > specific IP:PORT. I've tried two listen directives in server block: >by pva - Nginx Mailing List - English
Hi. After we enabled HTTP/2 in nginx some old software started to fail. So we would like to have HTTP v2 enabled in general but disabled for some specific IP:PORT. I've tried two listen directives in server block: listen IP:443 ssl http2; listen IP:1443 ssl; The problem is that on both ports I see: * ALPN: offers h2. Is it possible to disable HTTP v2 for specific IP:PORT? Thanks in advby pva - Nginx Mailing List - English
Hi, any ideas here? -- Peter. On Wed, Oct 13, 2021 at 1:12 PM Peter Volkov <peter.volkov@gmail.com> wrote: > Hi. > > We use Nginx as a reverse proxy for our service that manages CORS by > itself. Yet we have problems with errors that Nginx generates itself, e.g. > 413 Request Entity Too Large. Such error pages has no CORS headers and this > causes browsers to report theby pva - Nginx Mailing List - English
Hi. We use Nginx as a reverse proxy for our service that manages CORS by itself. Yet we have problems with errors that Nginx generates itself, e.g. 413 Request Entity Too Large. Such error pages has no CORS headers and this causes browsers to report the CORS issue, and thus the user does not see the real reason for this problem. So we would like to add permissive CORS headers to all error pages tby pva - Nginx Mailing List - English
Err, After few hours of debugging, and writing email here, I've realised that I have `gzip off;` in http {} block of configuration. After enabling gzip in http block everything works fine. Is it correct behaviour that no warning is issued with such configuration? -- Peter. On Tue, May 11, 2021 at 6:09 PM Peter Volkov <peter.volkov@gmail.com> wrote: > Hi, I have a HTTP/1.0 web server tby pva - Nginx Mailing List - English
Hi, I have a HTTP/1.0 web server that streams chunked content to clients. It does not gzip content so I would like to use nginx as reverse proxy to compress output from this server. Yet, no matter what I do nginx is not compressing results. For nginx I'm using following config: server { gzip on; gzip_comp_level 5; gzip_http_version 1.0; gzip_buffers 4 32k; gzip_min_length 0;by pva - Nginx Mailing List - English
On Wed, Sep 5, 2018 at 3:25 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > On Wed, Sep 05, 2018 at 09:58:54AM +0300, Peter Volkov wrote: > > > Hi. Could you, please, explain. Why nginx sends 301 redirect for the > > following vhost: > > > > server { > > listen 80; > > server_name test.domain.tv http://test.m9.smotreshka.tv; > > > &gby pva - Nginx Mailing List - English
Hi. Could you, please, explain. Why nginx sends 301 redirect for the following vhost: server { listen 80; server_name test.domain.tv http://test.m9.smotreshka.tv; access_log off; location = /test/README.txt { alias /var/www/; } } Here is redirect: $ http http://test.domain.tv/test/README.txt HTTP/1.1 301 Moved Permanently Connection: keep-alive Content-Length: 178by pva - Nginx Mailing List - English
Hi, Maxim. Maxim Dounin Wrote: > That's because try_files is not a mechanism to "conditionally select > configurations"[1] like the rewrite module directives (including > "return"), but rather a way to choose which file will be used for > request processing. As such, try_files checks happen right before > actually returning the response, after variouby pva - Nginx Mailing List - English
Francis, thank you for you answer. > On Thu, Jan 11, 2018 at 03:32:07AM -0500, pva wrote: > I'm slightly guessing, so apologies if I mislead you and hopefully > someone else will correct this if necessary... > > > Hi. Could you, please, explain why limit_req in @limitspeed location > > is not working in case of redirect to @allowed virtual location and works >by pva - Nginx Mailing List - English
Hi. Could you, please, explain why limit_req in @limitspeed location is not working in case of redirect to @allowed virtual location and works in case I copy @allowed virtual location contents inside @limitspeed? ================= This configuration is not limiting speed at all ======================== location @allowed { root /store/; try_files /live$uri @localdvr;by pva - Nginx Mailing List - English