add configurable RRDP snapshot and delta timeouts
This commit is contained in:
@@ -55,7 +55,9 @@ those choices do not change the built-in defaults.
|
||||
| `ta-constraints-enabled` | Boolean | true | Apply explicit or adjacent TA constraints files. False skips all constraints loading and enforcement, including adjacent discovery; unused missing or malformed files are ignored. |
|
||||
| `ta-refresh-policy` | String | `allow-valid-cache` | On automatic TA download failure, permit a revalidated, usable cached certificate. `require-fresh` prohibits fallback. Does not replace fixed TA files. |
|
||||
| `max-ca-depth` | Nonnegative integer | 64 | Maximum CA validation-tree depth. Zero is accepted by configuration parsing, but is a depth limit, not unlimited traversal. Usually keep 64. |
|
||||
| `http-timeout-secs` | Nonnegative integer, seconds | 300 | HTTP fetch timeout. Zero is normalized to one second, not unlimited. Does not set the whole-run or rsync timeout. |
|
||||
| `http-timeout-secs` | Nonnegative integer, seconds | 10 | Timeout for RRDP notification, TA/TAL and other small HTTP requests. Snapshot/delta bodies use their resource-specific settings below. Zero is normalized to one second, not unlimited. Does not set the whole-run or rsync timeout. |
|
||||
| `rrdp-snapshot-timeout-secs` | Nonnegative integer, seconds | 600 | Timeout for downloading an RRDP snapshot response body. Zero is normalized to one second. Selected by the RRDP resource type, including after same-origin redirects. |
|
||||
| `rrdp-delta-timeout-secs` | Nonnegative integer, seconds | 180 | Timeout for downloading an RRDP delta response body. Zero is normalized to one second. Each delta resource uses this value; it is independent of the validation run's overall timeout. |
|
||||
| `http-root-cert` | Array of path strings | `[]` | Additional HTTP TLS root certificates in PEM format. Every file must be readable and parseable. Empty means no custom additions; system TLS trust remains. These are not RPKI TA certificates. |
|
||||
| `parallel-max-repo-sync-workers-global` | Positive integer | 8 | Global repository-sync worker count. Zero is rejected. |
|
||||
| `parallel-phase2-object-workers` | Positive integer | 8 | Phase-2 object-processing worker count. Zero is rejected. |
|
||||
@@ -279,7 +281,9 @@ TA refresh policy does not make an anchor with an explicit ta automatic.
|
||||
log-format = "json"
|
||||
log-level = "debug"
|
||||
log-progress-interval-secs = 0
|
||||
http-timeout-secs = 600
|
||||
http-timeout-secs = 10 # notification, TA/TAL and other small HTTP requests
|
||||
rrdp-snapshot-timeout-secs = 600
|
||||
rrdp-delta-timeout-secs = 180
|
||||
http-root-cert = ["tls/internal-root.pem"]
|
||||
parallel-phase2-object-workers = 4
|
||||
parallel-max-repo-sync-workers-global = 4
|
||||
@@ -290,6 +294,10 @@ parallel-repo-worker-queue-capacity = 1024
|
||||
Replace existing top-level settings; do not add duplicate keys. Prepare the
|
||||
custom TLS PEM file first, or keep [] when no extra roots are needed. This does
|
||||
not change the TAL public key, relax TA validation or disable system TLS checks.
|
||||
The snapshot and delta timeouts are selected per RRDP resource, not per
|
||||
validation invocation: an `auto` run may use the snapshot value for one
|
||||
repository and the delta value for another. RRDP notification and TA/TAL HTTP
|
||||
requests continue to use `http-timeout-secs`.
|
||||
|
||||
### 8.4 Validation policy and rsync transport: top-level fragment
|
||||
|
||||
|
||||
Reference in New Issue
Block a user