# Connection limits

Connection limits are server-only XML options shared by native TCP and HTTP. Database SET and SHOW SETTINGS do not manage or list them.

## Defaults

| Setting                      | Default    | Contract                                                  |
| ---------------------------- | ---------- | --------------------------------------------------------- |
| `max_connections`            | 128        | Positive concurrent connection limit.                     |
| `max_inflight_request_bytes` | 67,108,864 | Positive limit on admitted incoming request bytes.        |
| `request_read_timeout`       | 5 seconds  | Positive socket timeout; fractional seconds are accepted. |

## Native request timing

A native login must complete within the receive timeout. After authentication, an idle session can wait between requests: the next ordinary request deadline starts when its first byte arrives.

Occasional additional bytes do not restart that ordinary request deadline. Socket writes also use the configured timeout.

## HTTP and uploads

HTTP bounds complete headers and ordinary bodies, and each upload body frame. Upload support does not remove header or timeout limits.

See [admission limits](https://coordinatordb.com/docs/concepts/features/configuration/settings/server-overload), [native TCP](https://coordinatordb.com/docs/concepts/features/interfaces/tcp) and [HTTP](https://coordinatordb.com/docs/concepts/features/interfaces/http) for the resulting client behavior.