clawbot 8d96bd710b Send the request ID upstream and log it with each image ...

The fetcher sends the request ID chi's RequestID middleware put in the
context as X-Request-Id, next to User-Agent and Accept, and the
"upstream fetched", "image converted" and "image served" lines carry it
as request_id, as the request log line does. A fetch shared by several
requests runs with the first request's context values, so it carries
that request's ID; README says so where it describes the shared fetch.

Model: opus-5-5

2026-10-04 08:40:15 +00:00

..

blocked_networks_internal_test.go

feat: blocked_networks config and extended SSRF ranges (closes #67)

2026-09-22 00:43:27 +02:00

fetch_internal_test.go

Remove idle host semaphores and delete .meta with its variant (closes #87)

2026-10-04 07:11:31 +02:00

httpfetcher_internal_test.go

next -> main (1.0.0 milestone) (#105)

2026-09-21 09:31:54 +02:00

httpfetcher.go

Send the request ID upstream and log it with each image

2026-10-04 08:40:15 +00:00

max_connections_internal_test.go

Remove idle host semaphores and delete .meta with its variant (closes #87)

2026-10-04 07:11:31 +02:00

mock.go

next -> main (1.0.0 milestone) (#105)

2026-09-21 09:31:54 +02:00

request_id_internal_test.go

Test that the upstream fetch and image log lines carry the request ID

2026-10-04 08:40:15 +00:00