Re: Buffering issues with nginx

On Mon, Jul 17, 2017 at 02:06:27AM -0400, Dan34 wrote: Hi there, > No matter what configs I try, nginx still keeps buffering my requests. proxy_request_buffering (http://nginx.org/r/proxy_request_buffering) relates to nginx buffering the request from the client. proxy_buffering

Re: Response code 400 rather than 404

Hello! On Mon, Jul 17, 2017 at 12:09:58AM -0700, li...@lazygranch.com wrote: > I'm curious why this request got a 400 response rather than a 404. > > 400 123.160.235.162 - - [16/Jul/2017:22:56:30 +] "GET /currentsetting.htm > HTTP/1.1" 173 "-" "-" "-" > > log_format main '$status

Problem setting up ssl

Hi, I'm trying to setup ssl on my server and "nginx -t" reports no problem but the server is now listening on port 256 instead of 443. Any idea what is wrong ? Thanks, Etienne ___ nginx mailing list nginx@nginx.org

Re: Problem setting up ssl

Sorry for the noise - apparently the certicate is not yet fully working. E Le 2017-07-17 à 11:29, Etienne Robillard a écrit : Hi, I'm trying to setup ssl on my server and "nginx -t" reports no problem but the server is now listening on port 256 instead of 443. Any idea what is wrong ?

Re: Problem setting up ssl

On July 17, 2017 7:05:31 PM EDT, Etienne Robillard wrote: >It seems I have a problem with the SSL certificate chain, as per >whatsmychaincert.com. However my SSL certificate provider (Gandi) says >that the SSL certificate still needs to be attributed... I don't know >what

Re: Problem setting up ssl

Le 2017-07-17 à 19:30, Fabian A. Santiago a écrit : You likely need to concatenate your cert and your ca's intermediate root signing cert into one file and apply that as your nginx cert with your private key as such. Then reload nginx. Hi Fabian, Is this precisely whatsmychaincert.com is

Re: Problem setting up ssl

It seems I have a problem with the SSL certificate chain, as per whatsmychaincert.com. However my SSL certificate provider (Gandi) says that the SSL certificate still needs to be attributed... I don't know what to do at this point but to wait for a message from Gandi. Whatsmychaincert.com is

try_files and gzip_static

From my knowledge, try_files works with gzip_static if both compressed and uncompressed files exist, but with "gunzip on;", it doesn't seem like try_files becomes aware of this, and so it'll only serve either the compressed or uncompressed file. Any idea how to get around this? I can't serve the

Response code 400 rather than 404

I'm curious why this request got a 400 response rather than a 404. 400 123.160.235.162 - - [16/Jul/2017:22:56:30 +] "GET /currentsetting.htm HTTP/1.1" 173 "-" "-" "-" log_format main '$status $remote_addr - $remote_user [$time_local] "$request" ' '$body_bytes_sent

[njs] Trailer content after script is optional.

details: http://hg.nginx.org/njs/rev/bef6842774f6 branches: changeset: 386:bef6842774f6 user: Igor Sysoev date: Mon Jul 17 14:46:35 2017 +0300 description: Trailer content after script is optional. diffstat: njs/njs_parser.c | 16

[njs] Initialize njs_vm_opt_t structs to 0 to simplify options adding.

details: http://hg.nginx.org/njs/rev/182d765687ee branches: changeset: 387:182d765687ee user: Dmitry Volyntsev date: Mon Jul 17 15:29:02 2017 +0300 description: Initialize njs_vm_opt_t structs to 0 to simplify options adding. diffstat: nginx/ngx_http_js_module.c

[nginx] Parenthesized ASCII-related calculations.

details: http://hg.nginx.org/nginx/rev/e3723f2a11b7 branches: changeset: 7067:e3723f2a11b7 user: Valentin Bartenev date: Mon Jul 17 17:23:51 2017 +0300 description: Parenthesized ASCII-related calculations. This also fixes potential undefined behaviour in the range

[njs] Interactive shell.

details: http://hg.nginx.org/njs/rev/f2ecbe1c2261 branches: changeset: 388:f2ecbe1c2261 user: Dmitry Volyntsev date: Mon Jul 17 20:38:00 2017 +0300 description: Interactive shell. diffstat: Makefile| 26 ++ njs/njs.c