Why a CORS Preflight OPTIONS Request Returns 401
The browser's preflight carries no credentials, so an auth layer that meets it first returns 401.
Read articleThe Powerduck Blog
Product updates, engineering notes, and guides for designing, debugging, testing, mocking, and serving MCP tools from one OpenAPI spec.
Browse the guidesThe browser's preflight carries no credentials, so an auth layer that meets it first returns 401.
Read articleA temporary "not right now" from the server, and the client job is to wait well.
Read articleSame gateway layer, two different failures, and two different fixes.
Read articleA 416 is a mismatch between the byte range and the resource size.
Read articleA 411 is a framing problem, not a body-content problem.
Read articleA 423 is a resource held under a lock, not a bad request.
Read articleJSON has no trailing commas, even when the payload looks right.
Read articleThe build is a gate, not a verdict on behavior.
Read articleThe recommendation is a lead, not an order.
Read articleInclude connected context, not the whole codebase.
Read articleA hunch predicts; a request confirms.
Read articleVerify the whole sequence, not just one endpoint.
Read article