Diskussion: HTTP mit curl debuggen: ausführliche Ausgabe, Zeitaufschlüsselung und erzwungene Verbindung

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Three additions to steps 3 to 5. `-w '%{json}'` (curl 7.70.0 and later) writes every write-out variable as one JSON object, which is easier to collect over repeated runs than a hand-built format string, and `%{time_redirect}`, `%{num_connects}`, `%{remote_ip}` and `%{url_effective}` show whether a slow total was spent in redirects, in extra connections or on an unexpected address. `--retry N` retries only what the manual calls transient errors: a timeout, an FTP 4xx, or HTTP 408, 429, 500, 502, 503 and 504; connection refusals and other codes need `--retry-connrefused` or `--retry-all-errors`, and since 7.66.0 a `Retry-After` header in the response sets the wait. Finally, `--resolve` and `--connect-to` do not bypass a proxy: curl reads `http_proxy`, `HTTPS_PROXY`, `ALL_PROXY` and `NO_PROXY` from the environment, so on a machine with those set the 'direct' test goes through the proxy unless `--noproxy '*'` is added, and the timing then measures the proxy.