andwati 3a07c298f6 Harden Gitea write requests against dropped Content-Type ...

Runs from the GitHub runner were failing every migrate with 422
"[]: Empty Content-Type" while the same script worked from a local
network, so the header is being dropped in front of Gitea on the
public path rather than the payload being wrong.

- route POST/PATCH through one gitea_write helper: body via
  --data-binary @file (also keeps the PAT out of the process list),
  Expect: disabled, explicit charset, retry over HTTP/1.1 when the
  response still reports an empty Content-Type
- add DEBUG_HTTP=1 to dump request/response headers, tokens redacted
- move temp files into a mktemp -d cleaned by trap
- add a workflow preflight that POSTs JSON over HTTP/2 and HTTP/1.1 to
  show whether the header survives the trip
- drop the redundant chmod; the script is committed mode 100755

2026-08-19 08:39:43 +03:00

..

mirror-to-gitea.yml

Harden Gitea write requests against dropped Content-Type

2026-08-19 08:39:43 +03:00