scgi_pass_header

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

scgi_param

Syntax: scgi_param parameter value [if_not_empty]; Default: — Context: http, server, location Sets a parameter that should be passed to the SCGI 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 scgi_param directives defined on the current level. Standard CGI environment variables should be provided as SCGI headers, see the scgi_params file provided in the distribution:

scgi_no_cache

Syntax: scgi_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: scgi_no_cache $cookie_nocache $arg_nocache$arg_comment; scgi_no_cache $http_pragma $http_authorization; Can be used along with the scgi_cache_bypass directive.

scgi_pass

Syntax: scgi_pass address; Default: — Context: location, if in location Sets the address of an SCGI server. The address can be specified as a domain name or IP address, and a port: scgi_pass localhost:9000; or as a UNIX-domain socket path: scgi_pass unix:/tmp/scgi.socket; If a domain name resolves to several addresses, all of them will be used in a round-robin fashion. In addition, an address can be specified as a server group.

scgi_next_upstream_timeout

Syntax: scgi_next_upstream_timeout time; Default: scgi_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.

scgi_next_upstream_tries

Syntax: scgi_next_upstream_tries number; Default: scgi_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.

scgi_next_upstream

Syntax: scgi_next_upstream error | timeout | invalid_header | http_500 | http_503 | http_403 | http_404 | non_idempotent | off ...; Default: scgi_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 whil

scgi_max_temp_file_size

Syntax: scgi_max_temp_file_size size; Default: scgi_max_temp_file_size 1024m; Context: http, server, location When buffering of responses from the SCGI server is enabled, and the whole response does not fit into the buffers set by the scgi_buffer_size and scgi_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 scgi_temp_file_wr

scgi_limit_rate

Syntax: scgi_limit_rate rate; Default: scgi_limit_rate 0; Context: http, server, location This directive appeared in version 1.7.7. Limits the speed of reading the response from the SCGI 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 SCGI server, the overall rate will be twice as much as the specified limit. The limitation works only if buffering o

scgi_intercept_errors

Syntax: scgi_intercept_errors on | off; Default: scgi_intercept_errors off; Context: http, server, location Determines whether an SCGI 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.