uwsgi_next_upstream

Syntax: uwsgi_next_upstream error | timeout | invalid_header | http_500 | http_503 | http_403 | http_404 | non_idempotent | off ...; Default: uwsgi_next_upstream error timeout; Context: http, server, location Specifies in which cases a request should be passed to the next server: error an error occurred while establishing a connection with the server, passing a request to it, or reading the response header; timeout a timeout has occurred wh

uwsgi_modifier2

Syntax: uwsgi_modifier2 number; Default: uwsgi_modifier2 0; Context: http, server, location Sets the value of the modifier2 field in the uwsgi packet header.

uwsgi_modifier1

Syntax: uwsgi_modifier1 number; Default: uwsgi_modifier1 0; Context: http, server, location Sets the value of the modifier1 field in the uwsgi packet header.

uwsgi_max_temp_file_size

Syntax: uwsgi_max_temp_file_size size; Default: uwsgi_max_temp_file_size 1024m; Context: http, server, location When buffering of responses from the uwsgi server is enabled, and the whole response does not fit into the buffers set by the uwsgi_buffer_size and uwsgi_buffers directives, a part of the response can be saved to a temporary file. This directive sets the maximum size of the temporary file. The size of data written to the temporary file at a time is set by the uwsgi_temp_f

uwsgi_intercept_errors

Syntax: uwsgi_intercept_errors on | off; Default: uwsgi_intercept_errors off; Context: http, server, location Determines whether a uwsgi server responses with codes greater than or equal to 300 should be passed to a client or be intercepted and redirected to nginx for processing with the error_page directive.

uwsgi_ignore_headers

Syntax: uwsgi_ignore_headers field ...; Default: — Context: http, server, location Disables processing of certain response header fields from the uwsgi server. The following fields can be ignored: “X-Accel-Redirect”, “X-Accel-Expires”, “X-Accel-Limit-Rate” (1.1.6), “X-Accel-Buffering” (1.1.6), “X-Accel-Charset” (1.1.6), “Expires”, “Cache-Control”, “Set-Cookie” (0.8.44), and “Vary” (1.7.7). If not disabled, processing of these header fields has the following effect: “X-Accel-Exp

uwsgi_limit_rate

Syntax: uwsgi_limit_rate rate; Default: uwsgi_limit_rate 0; Context: http, server, location This directive appeared in version 1.7.7. Limits the speed of reading the response from the uwsgi server. The rate is specified in bytes per second. The zero value disables rate limiting. The limit is set per a request, and so if nginx simultaneously opens two connections to the uwsgi server, the overall rate will be twice as much as the specified limit. The limitation works only if bufferi

uwsgi_ignore_client_abort

Syntax: uwsgi_ignore_client_abort on | off; Default: uwsgi_ignore_client_abort off; Context: http, server, location Determines whether the connection with a uwsgi server should be closed when a client closes the connection without waiting for a response.

uwsgi_hide_header

Syntax: uwsgi_hide_header field; Default: — Context: http, server, location By default, nginx does not pass the header fields “Status” and “X-Accel-...” from the response of a uwsgi server to a client. The uwsgi_hide_header directive sets additional fields that will not be passed. If, on the contrary, the passing of fields needs to be permitted, the uwsgi_pass_header directive can be used.

uwsgi_cache_valid

Syntax: uwsgi_cache_valid [code ...] time; Default: — Context: http, server, location Sets caching time for different response codes. For example, the following directives uwsgi_cache_valid 200 302 10m; uwsgi_cache_valid 404 1m; set 10 minutes of caching for responses with codes 200 and 302 and 1 minute for responses with code 404. If only caching time is specified uwsgi_cache_valid 5m; then only 200, 301, and 302 responses are cached. In addition, the any paramete