Bump HTTP read timeout to match reality of Bitcoin Core blocking

This commit is contained in:
Matt Corallo 2021-09-21 18:48:33 +00:00
parent 8f78bbda89
commit 0021320e7b

View file

@ -27,9 +27,10 @@ const TCP_STREAM_TIMEOUT: Duration = Duration::from_secs(5);
/// Timeout for reading the first byte of a response. This is separate from the general read /// Timeout for reading the first byte of a response. This is separate from the general read
/// timeout as it is not uncommon for Bitcoin Core to be blocked waiting on UTXO cache flushes for /// timeout as it is not uncommon for Bitcoin Core to be blocked waiting on UTXO cache flushes for
/// upwards of a minute or more. Note that we always retry once when we time out, so the maximum /// upwards of 10 minutes on slow devices (e.g. RPis with SSDs over USB). Note that we always retry
/// time we allow Bitcoin Core to block for is twice this value. /// once when we time out, so the maximum time we allow Bitcoin Core to block for is twice this
const TCP_STREAM_RESPONSE_TIMEOUT: Duration = Duration::from_secs(120); /// value.
const TCP_STREAM_RESPONSE_TIMEOUT: Duration = Duration::from_secs(300);
/// Maximum HTTP message header size in bytes. /// Maximum HTTP message header size in bytes.
const MAX_HTTP_MESSAGE_HEADER_SIZE: usize = 8192; const MAX_HTTP_MESSAGE_HEADER_SIZE: usize = 8192;