chore(server): spell out the coverage pin and drop a dash from the redirect note

Wording only: the comment over the new coverage entries and the safeFetch doc comment it shares a change with.
This commit is contained in:
Maurice
2026-10-08 12:00:04 +02:00
parent a86aa4e819
commit 30bdcf061b
2 changed files with 4 additions and 4 deletions
+1 -1
View File
@@ -447,7 +447,7 @@ export function capResponse(response: Response, maxBytes: number | null): Respon
* Redirects are followed through safeFetchFollow, so every hop is re-checked and
* re-pinned, with safeFetchFollow's defaults: a body cap and, for a call without
* a signal, a bounded wait for the headers. It used to hand the platform a
* `redirect: 'follow'` with a dispatcher pinned to the FIRST hop only — the same shape as
* `redirect: 'follow'` with a dispatcher pinned to the FIRST hop only, the same shape as
* GHSA-8mw6-xphx-886m, and pinning does not help there because Node skips the
* pinned lookup for an IP-literal host. Sixteen callers ride on this, several
* with a URL out of a per-user setting (Immich, Synology, AirTrail), and one