Ch. 20 · Networking

HTTP Preflight Requests and Allowed Operations

HTTP Preflight Requests and Allowed Operations. Learn the reasoning, a practical example, common mistakes and an interview exercise.

~2 min readintermediateupdated Oct 3, 2026

Browsers preflight certain cross-origin requests to ask whether the intended method and headers are permitted. The actual operation follows only under suitable responses.

Before you start

You should understand clients, servers, IP addresses and ports. Follow a request through name resolution, connection establishment and application exchange. Distinguish protocol guarantees from deployment policy, and use observations from the relevant layer rather than guessing from one browser error message.

The practical goal is to reason through this situation: A custom authorization header can require preflight before the main request. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.

Step-by-step walkthrough

Step 1: Read requested method and headers

The browser asks whether the intended cross-origin operation is allowed.

Step 2: Inspect OPTIONS behavior

Routing and allowed headers must support the preflight contract.

Step 3: Verify credentials policy

Allowed origin and credential behavior must be consistent.

Worked scenario

A custom authorization header can require preflight before the main request.

A request adds Authorization, triggering preflight under the browser’s rules. The API handles POST correctly but returns an unsuitable OPTIONS response, so the browser never performs the intended main call. Diagnose the preflight network entry first rather than changing the backend’s already working POST handler blindly.

Common mistake

Handling only the main method leaves the browser blocked before the application call.

Verify the behavior

Inspect requested headers, allowed response values and whether the main request was actually sent.

Interview exercise

Diagnose a preflight failure.

Answer and reasoning

Check the OPTIONS response, requested method and headers, allowed origin and credential policy.

Continue learning

Compare the scenario with the Networking interview questions and test your understanding with the Networking MCQs. For terminology and implementation details, consult the reference material.

More in Networking

read ✓Networking · mid

Networking: DNS Caching and TTL

Understand positive and negative caching, why changes are not instant, and how TTL trades propagation speed against query load.

~2 min readread →
read ✓Networking · easy

Networking: DNS Record Types

Read and choose DNS records: A and AAAA for addresses, CNAME for aliases, and MX and TXT for mail and verification.

~2 min readread →
read ✓Networking · mid

Networking: HTTP Redirects

Choose between 301, 302, 307 and 308, know which preserve the request method, and avoid caching and loop mistakes.

~2 min readread →
esc