Send Content-Type once on a delivery #331

Merged
clawbot merged 2 commits from issue-246-single-content-type into next 2026-09-29 07:11:56 +02:00
2 Commits
Author SHA1 Message Date
clawbot 2ae6f4be30 Cover the kept Content-Type in the origin-scoped names test
check / check (push) Successful in 4m55s
TestApplyRequestHeaders_ReportsOriginScopedNames now configures a
Content-Type on the target and asserts it is not among the returned
names, so dropping the delete in applyRequestHeaders fails it. Its
comment now says the inbound Content-Type is absent because it is not
forwarded.

Model: opus-5-5
2026-09-29 04:15:07 +00:00
clawbot 95499e2a59 Send Content-Type once on a delivery (closes #246)
A delivery set Content-Type from the event's ContentType and then
added the inbound Content-Type from the event's stored headers, so
the target could receive two values. The inbound Content-Type is no
longer forwarded from the stored headers; the receiver already saved
it as the event's ContentType.

Which value wins is now stated at applyRequestHeaders: a Content-Type
configured on the target, otherwise the event's ContentType,
otherwise none.

Model: opus-5-5
2026-09-29 04:15:07 +00:00