autocert checks the host policy before the token and answers 403 — the internal authority does this for every public name, so mail.novox.be's challenge died on the internal manager's probe one commit after it stopped dying on the public one's 404 (found live: the fall-through returned the internal policy's own "no internal-only route" text). Both shapes of refusal now fall through to routing; a fifth test pins the 403 case with a refusing policy.
autocert checks the host policy *before* the token and answers 403 — the internal authority does this for every public name, so `mail.novox.be`'s challenge died on the internal manager's probe one commit after it stopped dying on the public one's 404 (found live: the fall-through returned the internal policy's own "no internal-only route" text). Both shapes of refusal now fall through to routing; a fifth test pins the 403 case with a refusing policy.
autocert checks the host policy before the token and answers 403 — the
internal authority does this for every public name, so mail.novox.be's
challenge died on the internal manager's probe one commit after it
stopped dying on the public one's 404. Both shapes of refusal now fall
through to routing; a fifth test pins the 403 case with a refusing
policy.
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 checks the host policy before the token and answers 403 — the internal authority does this for every public name, so
mail.novox.be's challenge died on the internal manager's probe one commit after it stopped dying on the public one's 404 (found live: the fall-through returned the internal policy's own "no internal-only route" text). Both shapes of refusal now fall through to routing; a fifth test pins the 403 case with a refusing policy.