<!-- review: finished -->

<a id="http-uwsgi"></a>

# uWSGI

Allows passing requests to a uWSGI server.

<a id="configuration-example-48"></a>

## Configuration Example

```nginx
location / {
    include    uwsgi_params;
    uwsgi_pass localhost:9000;
}
```

<a id="directives-51"></a>

## Directives

<a id="index-0"></a>

<a id="uwsgi-bind"></a>

### uwsgi_bind

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_bind` address [`transparent`] | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------------------------|
| Default                                                                                  | —                                               |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                          |

Makes outgoing connections to a uWSGI server originate from the specified local IP address with an optional port. Parameter value can contain variables. The special value `off` cancels the effect of the uwsgi_bind directive inherited from the previous configuration level, which allows the system to auto-assign the local IP address and port.

The `transparent` parameter allows outgoing connections to a uWSGI server originate from a non-local IP address, for example, from a real IP address of a client:

```nginx
uwsgi_bind $remote_addr transparent;
```

In order for this parameter to work, it is usually necessary to run Angie worker processes with the [superuser](https://en.angie.software//angie/docs/configuration/modules/core.md#user) privileges. On Linux it is not required as if the `transparent` parameter is specified, worker processes inherit the CAP_NET_RAW capability from the master process.

#### NOTE
It is necessary to configure kernel routing table to intercept network traffic from the uWSGI server.

<a id="index-1"></a>

<a id="uwsgi-buffer-size"></a>

### uwsgi_buffer_size

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_buffer_size` size;   |
|------------------------------------------------------------------------------------------|-----------------------------|
| Default                                                                                  | `uwsgi_buffer_size 4k|8k;`  |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location      |

Sets the size of the buffer used for reading the first part of the response received from the uWSGI server. This part usually contains a small response header. By default, the buffer size is equal to one memory page. This is either 4K or 8K, depending on a platform. It can be made smaller, however.

<a id="index-2"></a>

<a id="uwsgi-buffering"></a>

### uwsgi_buffering

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_buffering` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-----------------------------------|
| Default                                                                                  | `uwsgi_buffering on;`             |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location            |

Enables or disables buffering of responses from the uWSGI server.

| `on`   | Angie receives a response from the uWSGI server as soon as possible, saving it into the buffers set by the [uwsgi_buffer_size](#uwsgi-buffer-size) and [uwsgi_buffers](#uwsgi-buffers) directives. Sending to the client is performed in parallel: filled buffers are passed for sending, but their total size is limited by [uwsgi_busy_buffers_size](#uwsgi-busy-buffers-size). If a buffer is not completely filled, it is not passed for sending unless it contains the last part of the response. Therefore, buffered reading is not suitable when you need immediate delivery of every few bytes. If the whole response does not fit into memory, a part of it can be saved to a [temporary file](#uwsgi-temp-path) on the disk. Writing to temporary files is controlled by the [uwsgi_max_temp_file_size](#uwsgi-max-temp-file-size) and [uwsgi_temp_file_write_size](#uwsgi-temp-file-write-size) directives.   |
|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `off`  | The response is passed to a client immediately as it is received. Angie works in a "read — send" loop and does not wait for the buffer to fill completely: for example, 10 bytes read from a 4K buffer are sent right away. At the same time, if the entire response fits into the buffer, Angie can read it in full. The maximum size of the data that Angie can receive from the server at a time is set by the [uwsgi_buffer_size](#uwsgi-buffer-size) directive. With `off`, [uwsgi_limit_rate](#uwsgi-limit-rate) does not work.                                                                                                                                                                                                                                                                                                                                                                                    |

Buffering can also be enabled or disabled by passing "yes" or "no" in the `X-Accel-Buffering` response header field. This capability can be disabled using the [uwsgi_ignore_headers](#uwsgi-ignore-headers) directive.

<a id="index-3"></a>

<a id="uwsgi-buffers"></a>

### uwsgi_buffers

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_buffers` number size;   |
|------------------------------------------------------------------------------------------|--------------------------------|
| Default                                                                                  | `uwsgi_buffers 8 4k | 8k;`     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location         |

Sets the number and size of the buffers used for reading a response from the uWSGI server, for a single connection.

By default, the buffer size is equal to one memory page. This is either 4K or 8K, depending on a platform.

<a id="index-4"></a>

<a id="uwsgi-busy-buffers-size"></a>

### uwsgi_busy_buffers_size

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_busy_buffers_size` size;     |
|------------------------------------------------------------------------------------------|-------------------------------------|
| Default                                                                                  | `uwsgi_busy_buffers_size 8k | 16k;` |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location              |

When [buffering](#uwsgi-buffering) of responses from the uWSGI server is enabled, limits the total size of buffers that can be busy sending a response to the client while the response is not yet fully read. In the meantime, the rest of the buffers can be used for reading the response and, if needed, buffering part of the response to a temporary file.

By default, size is limited by the size of two buffers set by the [uwsgi_buffer_size](#uwsgi-buffer-size) and [uwsgi_buffers](#uwsgi-buffers) directives.

<a id="index-5"></a>

<a id="uwsgi-cache"></a>

### uwsgi_cache

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache` zone | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------|
| Default                                                                                  | `uwsgi_cache off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location        |

Defines a shared memory zone used for caching. The same zone can be used in several places. Parameter value can contain variables.

| `off`   | disables caching inherited from the previous configuration level.   |
|---------|---------------------------------------------------------------------|

<a id="index-6"></a>

<a id="uwsgi-cache-background-update"></a>

### uwsgi_cache_background_update

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_background_update` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------------------------|
| Default                                                                                  | `uwsgi_cache_background_update off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                          |

Allows starting a background subrequest to update an expired cache item, while a stale cached response is returned to the client.

#### WARNING
Note that it is necessary to [allow](#uwsgi-cache-use-stale-updating) the usage of a stale cached response when it is being updated.

<a id="index-7"></a>

<a id="uwsgi-cache-bypass"></a>

### uwsgi_cache_bypass

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_bypass` ...;   |
|------------------------------------------------------------------------------------------|-----------------------------|
| Default                                                                                  | —                           |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location      |

Defines conditions under which the response will not be taken from 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 taken from the cache:

```nginx
uwsgi_cache_bypass $cookie_nocache $arg_nocache$arg_comment;
uwsgi_cache_bypass $http_pragma    $http_authorization;
```

Can be used along with the [uwsgi_no_cache](#uwsgi-no-cache) directive.

<a id="index-8"></a>

<a id="uwsgi-cache-key"></a>

### uwsgi_cache_key

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_key` string;   |
|------------------------------------------------------------------------------------------|-----------------------------|
| Default                                                                                  | —                           |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location      |

Defines a key for caching, for example

```nginx
uwsgi_cache_key localhost:9000$request_uri;
```

<a id="index-9"></a>

<a id="uwsgi-cache-lock"></a>

### uwsgi_cache_lock

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_lock` `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------|
| Default                                                                                  | `uwsgi_cache_lock off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location             |

When enabled, only one request at a time will be allowed to populate a new cache element identified according to the [uwsgi_cache_key](#uwsgi-cache-key) directive by passing a request to a uWSGI server. Other requests of the same cache element will either wait for a response to appear in the cache or the cache lock for this element to be released, up to the time set by the [uwsgi_cache_lock_timeout](#uwsgi-cache-lock-timeout) directive.

<a id="index-10"></a>

<a id="uwsgi-cache-lock-age"></a>

### uwsgi_cache_lock_age

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_lock_age` time;   |
|------------------------------------------------------------------------------------------|--------------------------------|
| Default                                                                                  | `uwsgi_cache_lock_age 5s;`     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location         |

If the last request passed to the uWSGI server for populating a new cache element has not completed for the specified time, one more request may be passed to the uWSGI server.

<a id="index-11"></a>

<a id="uwsgi-cache-lock-timeout"></a>

### uwsgi_cache_lock_timeout

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_lock_timeout` time;   |
|------------------------------------------------------------------------------------------|------------------------------------|
| Default                                                                                  | `uwsgi_cache_lock_timeout 5s;`     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location             |

Sets a timeout for [uwsgi_cache_lock](#uwsgi-cache-lock). When the time expires, the request will be passed to the uWSGI server, however, the response will not be cached.

<a id="index-12"></a>

<a id="uwsgi-cache-max-range-offset"></a>

### uwsgi_cache_max_range_offset

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_max_range_offset` number;   |
|------------------------------------------------------------------------------------------|------------------------------------------|
| Default                                                                                  | —                                        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                   |

Sets an offset in bytes for byte-range requests. If the range is beyond the offset, the range request will be passed to the uWSGI server and the response will not be cached.

<a id="index-13"></a>

<a id="uwsgi-cache-methods"></a>

### uwsgi_cache_methods

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_methods` `GET` | `HEAD` | `POST` ...;   |
|------------------------------------------------------------------------------------------|------------------------------------------------------|
| Default                                                                                  | `uwsgi_cache_methods GET HEAD;`                      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                               |

If the client request method is listed in this directive then the response will be cached. "GET" and "HEAD" methods are always added to the list, though it is recommended to specify them explicitly. See also the [uwsgi_no_cache](#uwsgi-no-cache) directive.

<a id="index-14"></a>

<a id="uwsgi-cache-min-uses"></a>

### uwsgi_cache_min_uses

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_min_uses` number;   |
|------------------------------------------------------------------------------------------|----------------------------------|
| Default                                                                                  | `uwsgi_cache_min_uses 1;`        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location           |

Sets the number of requests after which the response will be cached.

#### WARNING
Cache metadata is stored in shared memory. Manually deleting cache files does
not reset the counters and may lead to unpredictable behavior. To
completely reset the cache, stop the server, delete the cache directory, and start again.

#### NOTE
Third-party cache purge modules (e.g., [Cache Purge](https://en.angie.software//angie/docs/installation/external-modules/cache-purge.md#external-cache-purge)) only delete
files but do not reset the uwsgi_cache_min_uses counter. The directive
is intended to protect the cache from pollution by infrequent requests, and resetting
the counter on purge could negatively impact performance.

<a id="index-15"></a>

<a id="uwsgi-cache-path"></a>

### uwsgi_cache_path

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_path` path [`levels=`levels] [`use_temp_path=``on` | `off`] `keys_zone=`name:size [`inactive=`time] [`max_size=`size] [`min_free=`size] [`manager_files=`number] [`manager_sleep=`time] [`manager_threshold=`time] [`loader_files=`number] [`loader_sleep=`time] [`loader_threshold=`time];   |
|------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Default                                                                                  | —                                                                                                                                                                                                                                                                                                          |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http                                                                                                                                                                                                                                                                                                       |

Sets the path and other parameters of a cache. Cache data are stored in files. The file name in a cache is a result of applying the MD5 function to the [cache key](#uwsgi-cache-key).

The `levels` parameter defines hierarchy levels of a cache: from 1 to 3, each level accepts values 1 or 2. For example, in the following configuration:

```nginx
uwsgi_cache_path /data/angie/cache levels=1:2 keys_zone=one:10m;
```

file names in a cache will look like this:

```nginx
/data/angie/cache/c/29/b7f54b2df7773722d382f4809d65029c
```

A cached response is first written to a temporary file, and then the file is renamed. Temporary files and the cache can be put on different file systems. However, be aware that in this case a file is copied across two file systems instead of the cheap renaming operation. It is thus recommended that for any given location both cache and a directory holding temporary files are put on the same file system.

The directory for temporary files is set based on the `use_temp_path` parameter.

| `on`   | If this parameter is omitted or set to the value on, the directory set by the [uwsgi_temp_path](#uwsgi-temp-path) directive for the given location will be used.   |
|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `off`  | Temporary files will be put directly in the cache directory.                                                                                                       |

In addition, all active keys and information about data are stored in a shared memory zone, whose name and size are configured by the `keys_zone` parameter. One megabyte zone can store about 8 thousand keys. Cache metadata is stored in shared memory.

Cached data that are not accessed during the time specified by the `inactive` parameter get removed from the cache regardless of their freshness.

By default, `inactive` is set to 10 minutes.

A special **cache manager** process monitors the maximum cache size and the minimum amount of free space on the file system with cache, and when the size is exceeded or there is not enough free space, it removes the least recently used data. The data is removed in iterations.

| `max_size`          | maximum threshold value for cache size                                                      |
|---------------------|---------------------------------------------------------------------------------------------|
| `min_free`          | minimum threshold value for free space on the filesystem with cache                         |
| `manager_files`     | maximum number of cache items deleted in one iteration<br/><br/>Default: `100`              |
| `manager_threshold` | limits the time of one iteration<br/><br/>Default: `200` milliseconds                       |
| `manager_sleep`     | time for which a pause is maintained between iterations<br/><br/>Default: `50` milliseconds |

One minute after Angie starts, a special **cache loader** process is activated, which loads information about previously cached data stored on the filesystem into the cache zone. Loading also occurs in iterations.

| `loader_files`     | maximum number of cache items to load in one iteration<br/><br/>Default: `100`              |
|--------------------|---------------------------------------------------------------------------------------------|
| `loader_threshold` | limits the time of one iteration<br/><br/>Default: `200` milliseconds                       |
| `loader_sleep`     | time for which a pause is maintained between iterations<br/><br/>Default: `50` milliseconds |

<a id="index-16"></a>

<a id="uwsgi-cache-revalidate"></a>

### uwsgi_cache_revalidate

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_revalidate` `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------------|
| Default                                                                                  | `uwsgi_cache_revalidate off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                   |

Enables revalidation of expired cache items using conditional requests with the `If-Modified-Since` and `If-None-Match` header fields.

<a id="index-17"></a>

<a id="uwsgi-cache-use-stale"></a>

### uwsgi_cache_use_stale

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_use_stale` `error` | `timeout` | `invalid_header` | `updating` | `http_500` | `http_503` |  `http_403` | `http_404` | `http_429` | `off` ...;   |
|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Default                                                                                  | `uwsgi_cache_use_stale off;`                                                                                                                                 |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                                                                                                                                       |

Determines in which cases a stale cached response can be used. The directive's parameters match the parameters of the [uwsgi_next_upstream](#uwsgi-next-upstream) directive.

| `error`    | Permits using a stale cached response if a uwsgi server to process a request cannot be selected.                                                                                        |
|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `updating` | Additional parameter, permits using a stale cached response if it is currently being updated. This allows minimizing the number of accesses to uwsgi servers when updating cached data. |

Using a stale cached response can also be enabled directly in the response header for a specified number of seconds after the response became stale:

* The [stale-while-revalidate](https://datatracker.ietf.org/doc/html/rfc5861#section-3) extension of the `Cache-Control` header field permits using a stale cached response if it is currently being updated.
* The [stale-if-error](https://datatracker.ietf.org/doc/html/rfc5861#section-4) extension of the `Cache-Control` header field permits using a stale cached response in case of an error.

#### NOTE
This method has lower priority than setting directive parameters.

To minimize the number of requests to uwsgi servers when populating a new cache element, the [uwsgi_cache_lock](#uwsgi-cache-lock) directive can be used.

<a id="index-18"></a>

<a id="uwsgi-cache-valid"></a>

### uwsgi_cache_valid

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_cache_valid` [code ...] time;   |
|------------------------------------------------------------------------------------------|----------------------------------------|
| Default                                                                                  | —                                      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                 |

Sets caching time for different response codes. For example, the following directives

```nginx
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,

```nginx
uwsgi_cache_valid 5m;
```

then only 200, 301, and 302 responses are cached.

In addition, it can be specified to cache any responses using the `any` parameter:

```nginx
uwsgi_cache_valid 200 302 10m;
uwsgi_cache_valid 301      1h;
uwsgi_cache_valid any      1m;
```

#### NOTE
Caching parameters can also be set directly in the response header. This method has higher priority than setting caching time using the directive.

* The `X-Accel-Expires` header field sets caching time of a response in seconds. The value 0 disables caching for a response. If the value starts with the @ prefix, it sets an absolute time in seconds since Epoch, up to which the response may be cached.
* If the header does not include the `X-Accel-Expires` field, caching parameters are determined by the `Expires` or `Cache-Control` header fields.
* A response with the `Set-Cookie` header field will not be cached.
* A response with the `Vary` header field with the special value "\*" will not be cached. A response with the `Vary` header field with another value will be cached taking into account the corresponding request header fields.

Processing of one or more of these header fields can be disabled using the [uwsgi_ignore_headers](#uwsgi-ignore-headers) directive.

<a id="index-19"></a>

<a id="uwsgi-connect-timeout"></a>

### uwsgi_connect_timeout

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_connect_timeout` time;   |
|------------------------------------------------------------------------------------------|---------------------------------|
| Default                                                                                  | `uwsgi_connect_timeout 60s;`    |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location          |

Defines a timeout for establishing a connection with a uwsgi server. It should be noted that this timeout cannot usually exceed 75 seconds.

<a id="index-20"></a>

<a id="uwsgi-connection-drop"></a>

### uwsgi_connection_drop

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_connection_drop` time | `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------------------|
| Default                                                                                  | `uwsgi_connection_drop off;`                   |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                         |

Configures termination of all connections to the proxied server if it has been removed from the group or marked as permanently unavailable as a result of a [reresolve](https://en.angie.software//angie/docs/configuration/modules/http/http_upstream.md#reresolve) process or [API command](https://en.angie.software//angie/docs/configuration/modules/http/http_api.md#api-config-methods) `DELETE`.

A connection is terminated when the next read or write event is processed for either the client or the proxied server.

Setting time enables a connection termination [timeout](https://en.angie.software//angie/docs/configuration/configfile.md#syntax);
with `on` set, connections are dropped immediately.

<a id="index-21"></a>

<a id="uwsgi-force-ranges"></a>

### uwsgi_force_ranges

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_force_ranges` `on` | `off`;   |
|------------------------------------------------------------------------------------------|--------------------------------------|
| Default                                                                                  | `uwsgi_force_ranges off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location               |

Enables byte-range support for both cached and uncached responses from a uwsgi server regardless of the presence of the `Accept-Ranges` field in these responses.

<a id="index-22"></a>

<a id="uwsgi-hide-header"></a>

### uwsgi_hide_header

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_hide_header` field;   |
|------------------------------------------------------------------------------------------|------------------------------|
| Default                                                                                  | —                            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location       |

By default, Angie does not pass the header fields `Date`, `Server`, `X-Pad`, 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, conversely, the passing of fields needs to be permitted, the [uwsgi_pass_header](#uwsgi-pass-header) directive can be used.

<a id="index-23"></a>

<a id="uwsgi-ignore-client-abort"></a>

### uwsgi_ignore_client_abort

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ignore_client_abort` `on` | `off`;   |
|------------------------------------------------------------------------------------------|---------------------------------------------|
| Default                                                                                  | `uwsgi_ignore_client_abort off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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.

<a id="index-24"></a>

<a id="uwsgi-ignore-headers"></a>

### uwsgi_ignore_headers

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ignore_headers` field ...;   |
|------------------------------------------------------------------------------------------|-------------------------------------|
| Default                                                                                  | —                                   |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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`, `X-Accel-Buffering`, `X-Accel-Charset`, `Expires`, `Cache-Control`, `Set-Cookie`, and `Vary`.

If not disabled, processing of these header fields has the following effect:

* `X-Accel-Expires`, `Expires`, `Cache-Control`, `Set-Cookie`, and `Vary` set the parameters of response [caching](#uwsgi-cache-valid);
* `X-Accel-Redirect` performs an [internal redirect](https://en.angie.software//angie/docs/configuration/modules/http/index.md#internal) to the specified URI;
* `X-Accel-Limit-Rate` sets the [rate limit](https://en.angie.software//angie/docs/configuration/modules/http/index.md#limit-rate) for transmission of a response to a client;
* `X-Accel-Buffering` enables or disables [buffering](#uwsgi-buffering) of a response;
* `X-Accel-Charset` sets the desired [charset](https://en.angie.software//angie/docs/configuration/modules/http/http_charset.md#id1) of a response.

<a id="index-25"></a>

<a id="uwsgi-intercept-errors"></a>

### uwsgi_intercept_errors

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_intercept_errors` `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------------|
| Default                                                                                  | `uwsgi_intercept_errors off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                   |

Determines whether uwsgi server responses with codes greater than or equal to 300 should be passed to a client or be intercepted and redirected to Angie for processing with the [error_page](https://en.angie.software//angie/docs/configuration/modules/http/index.md#error-page) directive.

<a id="index-26"></a>

<a id="uwsgi-limit-rate"></a>

### uwsgi_limit_rate

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_limit_rate` rate;   |
|------------------------------------------------------------------------------------------|----------------------------|
| Default                                                                                  | `uwsgi_limit_rate 0;`      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location     |

Limits the speed of reading the response from the uwsgi server.
The rate is specified in bytes per second; variables can be used.

| `0`   | disables rate limiting   |
|-------|--------------------------|

#### NOTE
The limit is set per a request, and so if Angie 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 [buffering](#uwsgi-buffering) of responses from the uwsgi server is enabled.

<a id="index-27"></a>

<a id="uwsgi-max-temp-file-size"></a>

### uwsgi_max_temp_file_size

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_max_temp_file_size` size;   |
|------------------------------------------------------------------------------------------|------------------------------------|
| Default                                                                                  | `uwsgi_max_temp_file_size 1024m;`  |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location             |

When [buffering](#uwsgi-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](#uwsgi-buffer-size) and [uwsgi_buffers](#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_file_write_size](#uwsgi-temp-file-write-size) directive.

| `0`   | disables buffering of responses to temporary files   |
|-------|------------------------------------------------------|

#### NOTE
This restriction does not apply to responses that will be [cached](#uwsgi-cache) or [stored on disk](#uwsgi-store).

<a id="index-28"></a>

<a id="uwsgi-modifier1"></a>

### uwsgi_modifier1

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_modifier1` number;   |
|------------------------------------------------------------------------------------------|-----------------------------|
| Default                                                                                  | `uwsgi_modifier1 0;`        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location      |

Sets the value of the modifier1 field in the uwsgi packet header.

<a id="index-29"></a>

<a id="uwsgi-modifier2"></a>

### uwsgi_modifier2

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_modifier2` number;   |
|------------------------------------------------------------------------------------------|-----------------------------|
| Default                                                                                  | `uwsgi_modifier2 0;`        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location      |

Sets the value of the modifier2 field in the uwsgi packet header.

<a id="index-30"></a>

<a id="uwsgi-next-upstream"></a>

### uwsgi_next_upstream

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_next_upstream` `error` | `timeout` | `invalid_header` | `http_500` | `http_503` | `http_403` | `http_404` | `http_429` | `non_idempotent` | `off` ...;   |
|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Default                                                                                  | `uwsgi_next_upstream error timeout;`                                                                                                                            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                                                                                                                                          |

Specifies in which cases a request should be passed to the next server in the [upstream](https://en.angie.software//angie/docs/configuration/modules/http/http_upstream.md#http-upstream) group:

| `error`          | a connection error, request transmission error, or response header reading error occurred;                                                                                                                                                                                                           |
|------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `timeout`        | a timeout occurred during connection establishment, request transmission, or response header reading;                                                                                                                                                                                                |
| `invalid_header` | the server returned an empty or invalid response;                                                                                                                                                                                                                                                    |
| `http_500`       | the server returned a response with code 500;                                                                                                                                                                                                                                                        |
| `http_503`       | the server returned a response with code 503;                                                                                                                                                                                                                                                        |
| `http_403`       | the server returned a response with code 403;                                                                                                                                                                                                                                                        |
| `http_404`       | the server returned a response with code 404;                                                                                                                                                                                                                                                        |
| `http_429`       | the server returned a response with code 429;                                                                                                                                                                                                                                                        |
| `non_idempotent` | normally, requests with [non-idempotent](https://datatracker.ietf.org/doc/html/rfc7231#section-4.2.2) methods (`POST`, `LOCK`, `PATCH`) are not passed to another server if a request to an upstream server has already been sent; enabling this parameter explicitly allows retrying such requests; |
| `off`            | disables passing a request to the next server.                                                                                                                                                                                                                                                       |

#### NOTE
It should be understood that passing a request to the next server is only possible if nothing has been sent to the client yet. That is, if an error or timeout occurs in the middle of the transmission of a response, fixing this is impossible.

The directive also defines what is considered an [unsuccessful attempt](https://en.angie.software//angie/docs/configuration/modules/http/http_upstream.md#max-fails) of communication with a server.

| `error`<br/><br/>`timeout`<br/><br/>`invalid_header`   | are always considered unsuccessful attempts, even if they are not specified in the directive   |
|--------------------------------------------------------|------------------------------------------------------------------------------------------------|
| `http_500`<br/><br/>`http_503`<br/><br/>`http_429`     | are considered unsuccessful attempts only if they are specified in the directive               |
| `http_403`<br/><br/>`http_404`                         | are never considered unsuccessful attempts                                                     |

Passing a request to the next server can be limited by the [number of tries](#uwsgi-next-upstream-tries) and by [time](#uwsgi-next-upstream-timeout).

<a id="index-31"></a>

<a id="uwsgi-next-upstream-timeout"></a>

### uwsgi_next_upstream_timeout

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_next_upstream_timeout` time;   |
|------------------------------------------------------------------------------------------|---------------------------------------|
| Default                                                                                  | `uwsgi_next_upstream_timeout 0;`      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                |

Limits the time during which a request can be passed to the [next](#uwsgi-next-upstream) server.

| `0`   | turns off this limitation   |
|-------|-----------------------------|

<a id="index-32"></a>

<a id="uwsgi-next-upstream-tries"></a>

### uwsgi_next_upstream_tries

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_next_upstream_tries` number;   |
|------------------------------------------------------------------------------------------|---------------------------------------|
| Default                                                                                  | `uwsgi_next_upstream_tries 0;`        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                |

Limits the number of possible tries for passing a request to the [next](#uwsgi-next-upstream) server.

| `0`   | turns off this limitation   |
|-------|-----------------------------|

<a id="index-33"></a>

<a id="uwsgi-no-cache"></a>

### uwsgi_no_cache

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_no_cache` string ...;   |
|------------------------------------------------------------------------------------------|--------------------------------|
| Default                                                                                  | —                              |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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:

```nginx
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](#uwsgi-cache-bypass) directive.

<a id="index-34"></a>

<a id="uwsgi-param"></a>

### uwsgi_param

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_param` parameter value [`if_not_empty`];   |
|------------------------------------------------------------------------------------------|---------------------------------------------------|
| Default                                                                                  | —                                                 |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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 configuration level if and only if there are no `uwsgi_param` directives defined on the current level.

Standard [CGI environment variables](https://datatracker.ietf.org/doc/html/rfc3875#section-4.1) should be provided as uwsgi headers, see the `uwsgi_params` file provided in the distribution:

```nginx
location / {
    include uwsgi_params;
#    ...
}
```

In the standard `uwsgi_params` file, `REQUEST_METHOD` is set to
`$upstream_request_method`.

If the directive is specified with `if_not_empty` then such a parameter will be passed to the server only if its value is not empty:

```nginx
uwsgi_param HTTPS $https if_not_empty;
```

<a id="index-35"></a>

<a id="uwsgi-pass"></a>

### uwsgi_pass

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_pass` [protocol://] address;   |
|------------------------------------------------------------------------------------------|---------------------------------------|
| Default                                                                                  | —                                     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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:

```nginx
uwsgi_pass localhost:9000;
uwsgi_pass uwsgi://localhost:9000;
uwsgi_pass suwsgi://[2001:db8::1]:9090;
```

or as a UNIX domain socket path specified after the word `unix` and enclosed in colons:

```nginx
uwsgi_pass unix:/tmp/uwsgi.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](https://en.angie.software//angie/docs/configuration/modules/http/http_upstream.md#http-upstream).

Parameter value can contain variables. In this case, if an address is specified as a domain name, the name is searched among the described server groups, and, if not found, is determined using a [resolver](https://en.angie.software//angie/docs/configuration/modules/http/index.md#resolver).

#### NOTE
If `uwsgi_pass` is specified in a `location` with a trailing slash in the prefix
(for example, `location /name/`),
and the [auto_redirect](https://en.angie.software//angie/docs/configuration/modules/http/index.md#auto-redirect) directive is set to `default`,
requests without a trailing slash will be redirected (`/name -> /name/`).

<a id="index-36"></a>

<a id="uwsgi-pass-header"></a>

### uwsgi_pass_header

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_pass_header` field ...;   |
|------------------------------------------------------------------------------------------|----------------------------------|
| Default                                                                                  | —                                |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location           |

Permits passing [otherwise disabled](#uwsgi-hide-header) header fields from a uwsgi server to a client.

<a id="index-37"></a>

<a id="uwsgi-pass-request-body"></a>

### uwsgi_pass_request_body

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_pass_request_body` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------------------|
| Default                                                                                  | `uwsgi_pass_request_body on;`             |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                    |

Indicates whether the original request body is passed to the uwsgi server. See also the [uwsgi_pass_request_headers](#uwsgi-pass-request-headers) directive.

<a id="index-38"></a>

<a id="uwsgi-pass-request-headers"></a>

### uwsgi_pass_request_headers

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_pass_request_headers` `on` | `off`;   |
|------------------------------------------------------------------------------------------|----------------------------------------------|
| Default                                                                                  | `uwsgi_pass_request_headers on;`             |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                       |

Enables or disables passing of header fields from the original request to the uwsgi server. See also the [uwsgi_pass_request_body](#uwsgi-pass-request-body) directive.

<a id="index-39"></a>

<a id="uwsgi-read-timeout"></a>

### uwsgi_read_timeout

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_read_timeout` time;   |
|------------------------------------------------------------------------------------------|------------------------------|
| Default                                                                                  | `uwsgi_read_timeout 60s;`    |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | 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.

<a id="index-40"></a>

<a id="uwsgi-request-buffering"></a>

### uwsgi_request_buffering

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_request_buffering` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------------------|
| Default                                                                                  | `uwsgi_request_buffering on;`             |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                    |

Enables or disables buffering of a client request body.

| `on`   | The request body is fully [read](https://en.angie.software//angie/docs/configuration/modules/http/index.md#client-body-buffer-size) from the client before sending the request to the uwsgi server.                      |
|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `off`  | The request body is sent to the uwsgi server immediately as it is received. In this case, the request cannot be passed to the [next server](#uwsgi-next-upstream) if Angie has already started sending the request body. |

When HTTP/1.1 chunked transfer encoding is used to send the original request body, then the request body will be buffered regardless of the directive value.

<a id="index-41"></a>

<a id="uwsgi-send-timeout"></a>

### uwsgi_send_timeout

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_send_timeout` time;   |
|------------------------------------------------------------------------------------------|------------------------------|
| Default                                                                                  | `uwsgi_send_timeout 60s;`    |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location       |

Sets a timeout for transmitting a request to the uwsgi server. The timeout is set only between two successive write operations, not for the transmission of the whole request. If the uwsgi server does not receive anything within this time, the connection is closed.

<a id="index-42"></a>

<a id="uwsgi-socket-keepalive"></a>

### uwsgi_socket_keepalive

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_socket_keepalive` `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------------|
| Default                                                                                  | `uwsgi_socket_keepalive off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                   |

Configures the "TCP keepalive" behavior for outgoing connections to a uwsgi server.

| `off`   | By default, the operating system's settings are in effect for the socket.   |
|---------|-----------------------------------------------------------------------------|
| `on`    | The SO_KEEPALIVE socket option is turned on for the socket.                 |

<a id="index-43"></a>

<a id="uwsgi-ssl-certificate"></a>

### uwsgi_ssl_certificate

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_certificate` file;   |
|------------------------------------------------------------------------------------------|---------------------------------|
| Default                                                                                  | —                               |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location          |

Specifies a file with the certificate in the PEM format used for authentication to a secured uwsgi server. Variables can be used in the file name.

<a id="index-44"></a>

<a id="uwsgi-ssl-certificate-cache"></a>

### uwsgi_ssl_certificate_cache

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_certificate_cache` `off`;<br/><br/>`uwsgi_ssl_certificate_cache` `max=`N [`inactive=`time] [`valid=`time];   |
|------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------|
| Default                                                                                  | `uwsgi_ssl_certificate_cache off;`                                                                                      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                                                                                                  |

Defines a cache that stores [SSL certificates](#uwsgi-ssl-certificate) and [secret keys](#uwsgi-ssl-certificate-key) specified using variables.

The directive supports the following parameters:

- `max` — sets the maximum number of elements in the cache. When the cache
  overflows, the least recently used (LRU) elements are removed.
- `inactive` — defines the time after which an element is removed if it
  has not been accessed. The default is 10 seconds.
- `valid` — defines the time during which a cached element is considered
  valid and can be reused. The default is 60 seconds. After this period,
  certificates are reloaded or revalidated.
- `off` — disables the cache.

Example:

```nginx
uwsgi_ssl_certificate       $uwsgi_ssl_server_name.crt;
uwsgi_ssl_certificate_key   $uwsgi_ssl_server_name.key;
uwsgi_ssl_certificate_cache max=1000 inactive=20s valid=1m;
```

<a id="index-45"></a>

<a id="uwsgi-ssl-certificate-key"></a>

### uwsgi_ssl_certificate_key

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_certificate_key` file;   |
|------------------------------------------------------------------------------------------|-------------------------------------|
| Default                                                                                  | —                                   |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location              |

Specifies a file with the secret key in the PEM format used for authentication to a secured uwsgi server.

The value `engine:`name`:id` can be specified instead of the file, which loads a secret key with a specified id from the OpenSSL engine name.

The value `store:scheme:id` can be specified instead of the file, which is used to load a secret key with a specified id and OpenSSL provider registered URI scheme, such as [pkcs11](https://datatracker.ietf.org/doc/html/rfc7512).

Variables can be used in the file name.

<a id="index-46"></a>

<a id="uwsgi-ssl-ciphers"></a>

### uwsgi_ssl_ciphers

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_ciphers` ciphers;   |
|------------------------------------------------------------------------------------------|--------------------------------|
| Default                                                                                  | `uwsgi_ssl_ciphers DEFAULT;`   |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location         |

Specifies the enabled ciphers for requests to a secured uwsgi server. The ciphers are specified in the format understood by the OpenSSL library.

The list of ciphers depends on the version of OpenSSL installed.
The full list can be viewed using the `openssl ciphers` command.

#### WARNING
The `uwsgi_ssl_ciphers` directive does *not* configure ciphers for TLS
1.3 when using OpenSSL. To tune TLS 1.3 ciphers with OpenSSL, use the
[uwsgi_ssl_conf_command](#uwsgi-ssl-conf-command) directive, which was added to support advanced
SSL configuration.

- In LibreSSL, TLS 1.3 ciphers *can* be configured using
  `uwsgi_ssl_ciphers`.
- In BoringSSL, TLS 1.3 ciphers cannot be configured at all.

<a id="index-47"></a>

<a id="uwsgi-ssl-conf-command"></a>

### uwsgi_ssl_conf_command

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_conf_command` name value;   |
|------------------------------------------------------------------------------------------|----------------------------------------|
| Default                                                                                  | —                                      |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                 |

Sets arbitrary OpenSSL configuration [commands](https://docs.openssl.org/master/man3/SSL_CONF_cmd/) when establishing a connection with a secured uwsgi server.

#### NOTE
The directive is supported when using OpenSSL 1.0.2 or higher.
To configure TLS 1.3 ciphers in OpenSSL, use the `ciphersuites` command.

Multiple uwsgi_ssl_conf_command directives can be specified on the same level. These directives are inherited from the previous configuration level if and only if there are no uwsgi_ssl_conf_command directives defined on the current level.

#### WARNING
Note that reconfiguring OpenSSL directly might result in unexpected behavior.

<a id="index-48"></a>

<a id="uwsgi-ssl-crl"></a>

### uwsgi_ssl_crl

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_crl` file;   |
|------------------------------------------------------------------------------------------|-------------------------|
| Default                                                                                  | —                       |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location  |

Specifies a file with revoked certificates (CRL) in the PEM format used to [verify](#uwsgi-ssl-verify) the certificate of the secured uwsgi server.

<a id="index-49"></a>

<a id="uwsgi-ssl-name"></a>

### uwsgi_ssl_name

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_name` name;                         |
|------------------------------------------------------------------------------------------|------------------------------------------------|
| Default                                                                                  | `uwsgi_ssl_name `host name from uwsgi_pass`;\` |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                         |

Allows overriding the server name used to [verify](#uwsgi-ssl-verify) the certificate of the secured uwsgi server and to be [passed through SNI](#uwsgi-ssl-server-name) when establishing a connection with the secured uwsgi server.

By default, the host name from the [uwsgi_pass](#uwsgi-pass) directive is used.

<a id="index-50"></a>

<a id="uwsgi-ssl-password-file"></a>

### uwsgi_ssl_password_file

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_password_file` file;   |
|------------------------------------------------------------------------------------------|-----------------------------------|
| Default                                                                                  | —                                 |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location            |

Specifies a file with passphrases for [secret keys](#uwsgi-ssl-certificate-key) where each passphrase is specified on a separate line. Passphrases are tried in turn when loading the key.

<a id="index-51"></a>

<a id="uwsgi-ssl-protocols"></a>

### uwsgi_ssl_protocols

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_protocols` [`SSLv2`] [`SSLv3`] [`TLSv1`] [`TLSv1.1`] [`TLSv1.2`] [`TLSv1.3`];   |
|------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|
| Default                                                                                  | `uwsgi_ssl_protocols TLSv1.2 TLSv1.3;`                                                     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                                                                     |

#### Versionchanged
Changed in version 1.2.0: `TLSv1.3` parameter added to default set.

Enables the specified protocols for requests to a secured uwsgi server.

<a id="index-52"></a>

<a id="uwsgi-ssl-server-name"></a>

### uwsgi_ssl_server_name

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_server_name` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-----------------------------------------|
| Default                                                                                  | `uwsgi_ssl_server_name off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                  |

Enables or disables passing the server name
set by the [uwsgi_ssl_name](#uwsgi-ssl-name) directive
via the
[Server Name Indication](http://en.wikipedia.org/wiki/Server_Name_Indication)
TLS extension
(SNI,
[RFC 6066](https://datatracker.ietf.org/doc/html/rfc6066.html))
while establishing a connection with the secured uwsgi server.

<a id="index-53"></a>

<a id="uwsgi-ssl-session-reuse"></a>

### uwsgi_ssl_session_reuse

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_session_reuse` `on` | `off`;   |
|------------------------------------------------------------------------------------------|-------------------------------------------|
| Default                                                                                  | `uwsgi_ssl_session_reuse on;`             |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                    |

Determines whether SSL sessions can be reused when working with the secured uwsgi server. If the errors "SSL3_GET_FINISHED:digest check failed" appear in the logs, try disabling session reuse.

<a id="index-54"></a>

<a id="uwsgi-ssl-trusted-certificate"></a>

### uwsgi_ssl_trusted_certificate

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_trusted_certificate` file;   |
|------------------------------------------------------------------------------------------|-----------------------------------------|
| Default                                                                                  | —                                       |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                  |

Specifies a file with trusted CA certificates in the PEM format used to [verify](#uwsgi-ssl-verify) the certificate of the uwsgi HTTPS server.

<a id="index-55"></a>

<a id="uwsgi-ssl-verify"></a>

### uwsgi_ssl_verify

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_verify` `on` | `off`;   |
|------------------------------------------------------------------------------------------|------------------------------------|
| Default                                                                                  | `uwsgi_ssl_verify off;`            |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location             |

Enables or disables verification of the uwsgi server certificate.

<a id="index-56"></a>

<a id="uwsgi-ssl-verify-depth"></a>

### uwsgi_ssl_verify_depth

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_ssl_verify_depth` number;   |
|------------------------------------------------------------------------------------------|------------------------------------|
| Default                                                                                  | `uwsgi_ssl_verify_depth 1;`        |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location             |

Sets the verification depth in the uwsgi server certificates chain.

<a id="index-57"></a>

<a id="uwsgi-store"></a>

### uwsgi_store

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_store` `on` | `off` | string;   |
|------------------------------------------------------------------------------------------|----------------------------------------|
| Default                                                                                  | `uwsgi_store off;`                     |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                 |

Enables saving of files to a disk.

| `on`   | saves files with paths corresponding to the directives [alias](https://en.angie.software//angie/docs/configuration/modules/http/index.md#alias) or [root](https://en.angie.software//angie/docs/configuration/modules/http/index.md#root)   |
|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `off`  | disables saving of files                                                                                                                                                                                                                    |

The file name can be set explicitly using the string with variables:

```nginx
uwsgi_store /data/www$original_uri;
```

The modification time of files is set according to the received `Last-Modified` response header field. The response is first written to a temporary file, and then the file is renamed. Temporary files and the persistent store can be put on different file systems. However, be aware that in this case a file is copied across two file systems instead of the cheap renaming operation. It is thus recommended that for any given location both saved files and a directory holding temporary files, set by the [uwsgi_temp_path](#uwsgi-temp-path) directive, are put on the same file system.

This directive can be used to create local copies of static unchangeable files, e.g.:

```nginx
location /images/ {
    root               /data/www;
    error_page         404 = /fetch$uri;
}

location /fetch/ {
    internal;

    uwsgi_pass         backend:9000;
    ...

    uwsgi_store        on;
    uwsgi_store_access user:rw group:rw all:r;
    uwsgi_temp_path    /data/temp;

    alias              /data/www/;
}
```

<a id="index-58"></a>

<a id="uwsgi-store-access"></a>

### uwsgi_store_access

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_store_access` users:permissions ...;   |
|------------------------------------------------------------------------------------------|-----------------------------------------------|
| Default                                                                                  | `uwsgi_store_access user:rw;`                 |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                        |

Sets access permissions for newly created files and directories, e.g.:

```nginx
uwsgi_store_access user:rw group:rw all:r;
```

If any `group` or `all` access permissions are specified then user
permissions may be omitted:

```nginx
uwsgi_store_access group:rw all:r;
```

<a id="index-59"></a>

<a id="uwsgi-temp-file-write-size"></a>

### uwsgi_temp_file_write_size

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_temp_file_write_size` size;   |
|------------------------------------------------------------------------------------------|--------------------------------------|
| Default                                                                                  | `uwsgi_temp_file_write_size 8k|16k;` |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location               |

Limits the size of data written to a temporary file at a time, when buffering of responses from the uwsgi server to temporary files is enabled. By default, size is limited by two buffers set by the [uwsgi_buffer_size](#uwsgi-buffer-size) and [uwsgi_buffers](#uwsgi-buffers) directives. The maximum size of a temporary file is set by the [uwsgi_max_temp_file_size](#uwsgi-max-temp-file-size) directive.

<a id="index-60"></a>

<a id="uwsgi-temp-path"></a>

### uwsgi_temp_path

| [Syntax](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)   | `uwsgi_temp_path` path [level1 [level2 [level3]]]\`;                                                                                                                            |
|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Default                                                                                  | `uwsgi_temp_path uwsgi_temp;`<br/>(the path depends on the [build parameter](https://en.angie.software//angie/docs/installation/sourcebuild.md#paths) `--http-uwsgi-temp-path`) |
| [Context](https://en.angie.software//angie/docs/configuration/configfile.md#configfile)  | http, server, location                                                                                                                                                          |

Defines a directory for storing temporary files with data received from uwsgi servers. Up to three-level subdirectory hierarchy can be used underneath the specified directory. For example, in the following configuration

```nginx
uwsgi_temp_path /spool/angie/uwsgi_temp 1 2;
```

a temporary file might look like this:

```nginx
/spool/angie/uwsgi_temp/7/45/00000123457
```

See also the use_temp_path parameter of the [uwsgi_cache_path](#uwsgi-cache-path) directive.