Commit Graph
4 Commits
Author SHA1 Message Date
sneak 7151954a56 Offer archive expiry choices on the target forms, show plain units (closes #396)
check / check (push) Successful in 3m26s
Adding or editing a database target now offers the archive expiry
choices of the new webhook page (never, 1h, 12h, 24h, 30d, 90d, 365d)
in place of a text field. The list is defined once, in
internal/handlers/archive_expiry.go, and all three forms render it. The
edit form starts on the expiry it shows: the stored one, or the
submitted one after a refused save. One that is not among the choices
is listed first as its own entry, so saving unchanged keeps it. The
target list shows the expiry in plain units, such as "30 days" or
"12 hours", or "never".

Model: opus-5-5
2026-10-02 23:01:46 +00:00
clawbot d4f4ddf51f Send Content-Type once on a delivery (closes #246)
check / check (push) Successful in 3m20s
A delivery set Content-Type from the event's ContentType and then
added the inbound Content-Type from the event's stored headers, so a
target could receive two values. The inbound Content-Type is no
longer forwarded from the stored headers; the receiver already saves
it as the event's ContentType.

Which value is sent is now stated at applyRequestHeaders: a
Content-Type configured on the target, otherwise the event's
ContentType, otherwise none. A configured one still survives a
cross-origin 307/308 with its body.

Model: opus-5-5
2026-09-29 07:11:55 +02:00
clawbot 687405993e Harden operator-set target headers (closes #233) (#242)
check / check (push) Successful in 2m58s
2026-08-20 10:54:43 +02:00
clawbot aba02bc509 Add a target edit form with headers and timeout fields (closes #127) (#229)
check / check (push) Failing after 2m59s
2026-08-20 07:24:12 +02:00