uwsgi_request_buffering

Syntax: uwsgi_request_buffering on | off; Default: uwsgi_request_buffering on; Context: http, server, location This directive appeared in version 1.7.11. Enables or disables buffering of a client request body. When buffering is enabled, the entire request body is read from the client before sending the request to a uwsgi server. When buffering is disabled, the request body is sent to the uwsgi server immediately as it is received. In this case, the request cannot be passed to

uwsgi_read_timeout

Syntax: uwsgi_read_timeout time; Default: uwsgi_read_timeout 60s; Context: http, server, location Defines a timeout for reading a response from the uwsgi server. The timeout is set only between two successive read operations, not for the transmission of the whole response. If the uwsgi server does not transmit anything within this time, the connection is closed.

uwsgi_pass_request_headers

Syntax: uwsgi_pass_request_headers on | off; Default: uwsgi_pass_request_headers on; Context: http, server, location Indicates whether the header fields of the original request are passed to the uwsgi server. See also the uwsgi_pass_request_body directive.

uwsgi_pass_request_body

Syntax: uwsgi_pass_request_body on | off; Default: uwsgi_pass_request_body on; Context: http, server, location Indicates whether the original request body is passed to the uwsgi server. See also the uwsgi_pass_request_headers directive.

uwsgi_pass_header

Syntax: uwsgi_pass_header field; Default: — Context: http, server, location Permits passing otherwise disabled header fields from a uwsgi server to a client.

uwsgi_pass

Syntax: uwsgi_pass [protocol://]address; Default: — Context: location, if in location Sets the protocol and address of a uwsgi server. As a protocol, “uwsgi” or “suwsgi” (secured uwsgi, uwsgi over SSL) can be specified. The address can be specified as a domain name or IP address, and a port: uwsgi_pass localhost:9000; uwsgi_pass uwsgi://localhost:9000; uwsgi_pass suwsgi://[2001:db8::1]:9090; or as a UNIX-domain socket path: uwsgi_pass unix:/tmp/uwsgi.socket; If a domain nam

uwsgi_param

Syntax: uwsgi_param parameter value [if_not_empty]; Default: — Context: http, server, location Sets a parameter that should be passed to the uwsgi server. The value can contain text, variables, and their combination. These directives are inherited from the previous level if and only if there are no uwsgi_param directives defined on the current level. Standard CGI environment variables should be provided as uwsgi headers, see the uwsgi_params file provided in the distribu

uwsgi_no_cache

Syntax: uwsgi_no_cache string ...; Default: — Context: http, server, location Defines conditions under which the response will not be saved to a cache. If at least one value of the string parameters is not empty and is not equal to “0” then the response will not be saved: uwsgi_no_cache $cookie_nocache $arg_nocache$arg_comment; uwsgi_no_cache $http_pragma $http_authorization; Can be used along with the uwsgi_cache_bypass directive.

uwsgi_next_upstream_tries

Syntax: uwsgi_next_upstream_tries number; Default: uwsgi_next_upstream_tries 0; Context: http, server, location This directive appeared in version 1.7.5. Limits the number of possible tries for passing a request to the next server. The 0 value turns off this limitation.

uwsgi_next_upstream_timeout

Syntax: uwsgi_next_upstream_timeout time; Default: uwsgi_next_upstream_timeout 0; Context: http, server, location This directive appeared in version 1.7.5. Limits the time during which a request can be passed to the next server. The 0 value turns off this limitation.