autocert.Manager.HTTPHandler answers 404 itself for a token it does not hold and never consults its fallback on the challenge path — the predecessor's exact fault ("the edge owns ACME"), rediscovered live when Mailu's renewal died behind this proxy on cutover day and served its April-expired certbot state to real IMAPS users (mesh-catalog #90/#91 are the flip and the revert).
tokenOrRoute probes each authority against a buffered writer and hands a token none of them holds to plain routing, so a consumer's own ACME client answers its own challenge through an ordinary path-scoped route. Four tests pin it: unknown token routes, held token answers, a second authority is probed past the first, ordinary paths never touch the machinery. The pre-existing foundation-manifest test failures on main are untouched.
`autocert.Manager.HTTPHandler` answers 404 itself for a token it does not hold and never consults its fallback on the challenge path — the predecessor's exact fault ("the edge owns ACME"), rediscovered live when Mailu's renewal died behind this proxy on cutover day and served its April-expired certbot state to real IMAPS users (mesh-catalog #90/#91 are the flip and the revert).
`tokenOrRoute` probes each authority against a buffered writer and hands a token none of them holds to plain routing, so a consumer's own ACME client answers its own challenge through an ordinary path-scoped route. Four tests pin it: unknown token routes, held token answers, a second authority is probed past the first, ordinary paths never touch the machinery. The pre-existing foundation-manifest test failures on main are untouched.
autocert's HTTPHandler answers 404 itself for a token it does not hold
and never consults its fallback on the challenge path — the
predecessor's exact fault, rediscovered live when Mailu's renewal died
behind this proxy on cutover day. tokenOrRoute probes each authority
against a buffered writer and hands a token none of them holds to plain
routing, so a consumer's own ACME client answers its own challenge
through an ordinary path-scoped route. Four tests pin it, including the
cache-key shape a restart-surviving token actually has.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
autocert.Manager.HTTPHandleranswers 404 itself for a token it does not hold and never consults its fallback on the challenge path — the predecessor's exact fault ("the edge owns ACME"), rediscovered live when Mailu's renewal died behind this proxy on cutover day and served its April-expired certbot state to real IMAPS users (mesh-catalog #90/#91 are the flip and the revert).tokenOrRouteprobes each authority against a buffered writer and hands a token none of them holds to plain routing, so a consumer's own ACME client answers its own challenge through an ordinary path-scoped route. Four tests pin it: unknown token routes, held token answers, a second authority is probed past the first, ordinary paths never touch the machinery. The pre-existing foundation-manifest test failures on main are untouched.