Syntax: proxy_pass_error_message on | off; Default: proxy_pass_error_message off; Context: mail, server Indicates whether to pass the error message obtained during the authentication on the backend to the client. Usually, if the authentication in nginx is a success, the backend cannot return an error. If it nevertheless returns an error, it means some internal error has occurred. In such case the backend message can contain information that should not be shown to the client. Howe

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

Syntax: proxy_pass URL; Default: — Context: location, if in location, limit_except Sets the protocol and address of a proxied server and an optional URI to which a location should be mapped. As a protocol, “http” or “https” can be specified. The address can be specified as a domain name or IP address, and an optional port: proxy_pass http://localhost:8000/uri/; or as a UNIX-domain socket path specified after the word “unix” and enclosed in colons: proxy_pass http://unix:/tmp/

Syntax: proxy_pass address; Default: — Context: server Sets the address of a proxied server. The address can be specified as a domain name or IP address, and a port: proxy_pass localhost:12345; or as a UNIX-domain socket path: proxy_pass unix:/tmp/stream.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. The address can also be specified using variables (1.1

Syntax: proxy_next_upstream_tries number; Default: proxy_next_upstream_tries 0; Context: stream, server Limits the number of possible tries for passing a connection to the next server. The 0 value turns off this limitation.

Syntax: proxy_next_upstream_tries number; Default: proxy_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.

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

Syntax: proxy_next_upstream_timeout time; Default: proxy_next_upstream_timeout 0; Context: stream, server Limits the time allowed to pass a connection to the next server. The 0 value turns off this limitation.

Syntax: proxy_next_upstream_timeout time; Default: proxy_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.

Syntax: proxy_next_upstream error | timeout | invalid_header | http_500 | http_502 | http_503 | http_504 | http_403 | http_404 | non_idempotent | off ...; Default: proxy_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; tim