September 01, 2016 10:47PM
Hi B.R

Please find the nginx confiuration below that we are using. and any help would be greatful.

nginx -V
=================
nginx version: nginx/1.8.0
built with OpenSSL 1.0.2h-fips 3 May 2016
TLS SNI support enabled
configure arguments: --crossbuild=Linux::arm --with-cc=arm-linux-gnueabihf-gcc --with-cpp=arm-linux-gnueabihf-gcc --with-cc-opt='-pipe -Os -gdwarf-4 -mfpu=neon --sysroot=/work/autobuild/project_hub_release/nginx/service/001.1635A/sol_aux_build/sbq_sysroot' --with-ld-opt=--sysroot=/work/autobuild/project_hub_release/nginx/service/001.1635A/sol_aux_build/sbq_sysroot --prefix=/usr --conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/sbin/nginx --pid-path=/var/run/nginx.pid --lock-path=/var/run/lock/nginx.lock --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --http-client-body-temp-path=/var/tmp/nginx/client-body --http-proxy-temp-path=/var/tmp/nginx/proxy --http-fastcgi-temp-path=/var/tmp/nginx/fastcgi --http-scgi-temp-path=/var/tmp/nginx/scgi --http-uwsgi-temp-path=/var/tmp/nginx/uwsgi --user=www-data --group=www-data --with-ipv6 --with-http_ssl_module --with-http_gzip_static_module --with-debug

nginx.conf
=================
worker_processes 1;

events {
worker_connections 1024;
}

http {
include mime.types;
default_type application/octet-stream;

sendfile on;

keepalive_timeout 65;

server {
listen 80;
listen [::]:80;
listen 8080;
listen [::]:8080;
listen 127.0.0.1:14200; #usb port
listen 443 ssl;
listen [::]:443 ssl;
listen 127.0.0.1:14199; # for internal LEDM requests to bypass authentication check
listen 127.0.0.1:6015; # websocket internal port to talk to nginx.

server_name localhost;

include /project/ram/secutils/*.conf;

include /project/rom/httpmgr_nginx/*.conf;

fastcgi_param PATH_INFO $fastcgi_path_info;
include fastcgi_params;

error_page 500 502 503 504 /50x.html;
location = /50x.html {
root html;
}
}

}

proj_server.conf:
=================

server {
listen [::]:5678 ssl ipv6only=off;

ssl_certificate /project/rw/cert_svc/dev_cert.pem;
ssl_certificate_key /mnt/encfs/cert_svc/dev_key.pem;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;

gzip on;
gzip_types *;
gzip_min_length 0;

# If the incoming request body is greater than client_max_body_size,
# NGINX will return 413 request entitiy too large.
# Setting to 0 will disable this size check.
client_max_body_size 0;

# By default, NGINX will try to buffer up the entire request body before
# sending it to the backend server.
# Turning it off should stop this behavior and pass the request on immediately.
fastcgi_request_buffering off;

# By default, NGINX will try to buffer up the entire response before
# sending it to the client.
# Turning it off should stop this behavior and pass the response on immediately.
fastcgi_buffering off;

# Default timeout is 60s and there is no way to disable the read timeout.
# If a read has not been performed in the specified interval
# a 504 response is sent from NGINX to the client.
# This could happen if there is a flow stoppage in the upstream.
fastcgi_read_timeout 7d;

# Default timeout is 60s and there is no way to disable the send timeout.
# If NGINX has not sent data to the FastCGI server in the specified interval
# a 504 response is sent from NGINX to the client.
# This could happen if there is a flow stoppage in the upstream.
fastcgi_send_timeout 7d;

# This server's listen directive says to use SSL on port 5678.
# When HTTP requests come to an SSL port NGINX throws a 497 HTTP Request Sent to HTTPS Port
# Since our requests will be HTTP on port 5678, NGINX will throw error code 497
# To fix this, when NGINX throws 497, we tell it to use the status code
# from the upstream server.
error_page 497 = $request_uri;

fastcgi_param PATH_INFO $fastcgi_path_info;
fastcgi_param HOST $host;
include fastcgi_params;

location = /path/to/resource1 {
fastcgi_pass 127.0.0.1:14052;
}

location = /path/to/resource2 {
fastcgi_pass 127.0.0.1:14052;
}

}
Subject Author Posted

how to completely disable request body buffering

Phani Sreenivasa Prasad August 26, 2016 01:22AM

Re: how to completely disable request body buffering

B.R. August 26, 2016 11:18AM

Re: how to completely disable request body buffering

Phani Sreenivasa Prasad September 01, 2016 10:47PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 136
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready