|
157 | 157 | | `insecure?` | if `true`, ignores the certificate for any `https://` domains
|
158 | 158 | | `response-buffer-size` | the amount of the response, in bytes, that is buffered before the request returns, defaults to `65536`. This does *not* represent the maximum size response that the client can handle (which is unbounded), and is only a means of maximizing performance.
|
159 | 159 | | `keep-alive?` | if `true`, attempts to reuse connections for multiple requests, defaults to `true`.
|
| 160 | + | `connect-timeout` | timeout for a connection to be established, in milliseconds. Default determined by Netty, see `aleph.netty/default-connect-timeout`. |
160 | 161 | | `idle-timeout` | when set, forces keep-alive connections to be closed after an idle time, in milliseconds.
|
161 | 162 | | `transport` | the transport to use, one of `:nio`, `:epoll`, `:kqueue` or `:io-uring` (defaults to `:nio`).
|
162 | 163 | | `raw-stream?` | if `true`, bodies of responses will not be buffered at all, and represented as Manifold streams of `io.netty.buffer.ByteBuf` objects rather than as an `InputStream`. This will minimize copying, but means that care must be taken with Netty's buffer reference counting. Only recommended for advanced users.
|
|
275 | 276 | | `pipeline-transform` | an optional function that takes an `io.netty.channel.ChannelPipeline` object, which represents a connection, and modifies it.
|
276 | 277 | | `max-frame-payload` | maximum allowable frame payload length, in bytes, defaults to `65536`.
|
277 | 278 | | `max-frame-size` | maximum aggregate message size, in bytes, defaults to `1048576`.
|
| 279 | + | `connect-timeout` | timeout for a connection to be established, in milliseconds. Default determined by Netty, see `aleph.netty/default-connect-timeout`. |
278 | 280 | | `bootstrap-transform` | an optional function that takes an `io.netty.bootstrap.Bootstrap` object and modifies it.
|
279 | 281 | | `transport` | the transport to use, one of `:nio`, `:epoll`, `:kqueue` or `:io-uring` (defaults to `:nio`).
|
280 | 282 | | `heartbeats` | optional configuration to send Ping frames to the server periodically (if the connection is idle), configuration keys are `:send-after-idle` (in milliseconds), `:payload` (optional, empty frame by default) and `:timeout` (optional, to close the connection if Pong is not received after specified timeout)."
|
|
342 | 344 |
|
343 | 345 | Param key | Description
|
344 | 346 | -------------------- | -----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
345 |
| - `connection-timeout` | timeout in milliseconds for the connection to become established |
| 347 | + `connection-timeout` | timeout in milliseconds for the connection to become established, defaults to 60s. Note that this timeout will be ineffective if the pool's `connect-timeout` is lower. |
346 | 348 | `follow-redirects?` | whether to follow redirects, defaults to `true`; see `aleph.http.client-middleware/handle-redirects`
|
347 | 349 | `middleware` | custom client middleware for the request
|
348 | 350 | `pool-timeout` | timeout in milliseconds for the pool to generate a connection
|
|
496 | 498 | | `follow-redirects?` | whether to follow redirects, defaults to `true`; see `aleph.http.client-middleware/handle-redirects`
|
497 | 499 | | `pool` | a custom connection pool
|
498 | 500 | | `pool-timeout` | timeout in milliseconds for the pool to generate a connection
|
499 |
| - | `connection-timeout` | timeout in milliseconds for the connection to become established |
| 501 | + | `connection-timeout` | timeout in milliseconds for the connection to become established, defaults to 60s. Note that this timeout will be ineffective if the pool's `connect-timeout` is lower. |
500 | 502 | | `request-timeout` | timeout in milliseconds for the arrival of a response over the established connection
|
501 | 503 | | `read-timeout` | timeout in milliseconds for the response to be completed
|
502 | 504 | | `response-executor` | optional `java.util.concurrent.Executor` that will handle the requests (defaults to a `flow/utilization-executor` of 256 `max-threads` and a `queue-length` of 0)")
|
|
0 commit comments