Answer 415 for a source whose first bytes do not match its Content-Type (closes #253)

Conversation 0 Commits 2 Files Changed 6

+243 -16

2 Commits

Author	SHA1	Message	Date
clawbot	6ebb6ed618	Answer 415 for a source whose first bytes do not match its Content-Type (closes #253 ) check / check (push) Waiting to run Details A body whose first bytes are not those of the format its Content-Type names answered 500 on both image routes, was logged as pixa's own error, and was fetched again on every request. Both routes now answer 415 for each error the first-bytes check returns, and the image service logs the refused source at warning level. The failure also gets a negative cache entry, as an upstream error status does, so the source URL is not fetched for 5 minutes and answers 502 meanwhile. README.md says so. TestService_Get_ConcurrentMissesShareAFailure still expects such a source to be fetched again and fails until its case is changed. Model: opus-5-5	2026-10-15 08:13:18 +00:00
clawbot	40387e90bb	Test that a source not matching its Content-Type answers 415 Both image routes must answer 415 for an upstream body whose first bytes are not those of the format its Content-Type names, log it as a refused source and not at error level, and answer the next request for that source 502 without fetching it again. The test fails until the fix for #253. Model: opus-5-5	2026-10-15 08:12:58 +00:00

Author

SHA1

Message

Date

clawbot

6ebb6ed618

Answer 415 for a source whose first bytes do not match its Content-Type (closes #253 )

check / check (push) Waiting to run

Details

A body whose first bytes are not those of the format its Content-Type
names answered 500 on both image routes, was logged as pixa's own
error, and was fetched again on every request. Both routes now answer
415 for each error the first-bytes check returns, and the image service
logs the refused source at warning level. The failure also gets a
negative cache entry, as an upstream error status does, so the source
URL is not fetched for 5 minutes and answers 502 meanwhile. README.md
says so.

TestService_Get_ConcurrentMissesShareAFailure still expects such a
source to be fetched again and fails until its case is changed.

Model: opus-5-5

2026-10-15 08:13:18 +00:00

clawbot

40387e90bb

Test that a source not matching its Content-Type answers 415

Both image routes must answer 415 for an upstream body whose first
bytes are not those of the format its Content-Type names, log it as a
refused source and not at error level, and answer the next request for
that source 502 without fetching it again. The test fails until the
fix for #253.

Model: opus-5-5

2026-10-15 08:12:58 +00:00

Answer 415 for a source whose first bytes do not match its Content-Type (closes #253) #273