Backend, Data & Security Core A1 · Official standard Platform: Web

Redirect

A Redirect sends a client from one address to another. Its status says whether the move is temporary or permanent.

See how it works
You might call it HTTP redirectURL forwardingrewrite destination

See how it works

Original worked exampleRedirect

Another example

After a guide moves, its old address permanently redirects to the exact replacement. Bookmarks and search signals remain useful.

Main parts

  1. 01Originating request
  2. 02Resolution or processing hop
  3. 03Response, timing, and failure

Use it when

Use redirects for moved resources, main hosts, protocol upgrades, or safe returns after sign-in.

Do not use it when

Avoid chains, loops, home-page fallbacks, and unvalidated external return URLs.

Name used in code

Location + 301 / 302 / 307 / 308

Before you ship

Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback.

Request you can copy

Outcome: Design or review Redirect for this system while keeping data correct, secure, and easy to operate. User context: After a guide moves, its old address permanently redirects to the exact replacement. Bookmarks and search signals remain useful. Technical concept or control: Redirect. Why it fits: Use redirects for moved resources, main hosts, protocol upgrades, or safe returns after sign-in. Do not use it when: Avoid chains, loops, home-page fallbacks, and unvalidated external return URLs. Engineering requirements: Define inputs, outputs, contracts, and rules that must always hold. Set authorization and input checks. Define failures, timeouts, retries, one-time effects, data moves, and compatibility limits. Operations: Add useful signals and logs that hide sensitive data. Set capacity limits and write an operator guide. Test recovery and rollback. Acceptance criteria: Contract and failure-path tests pass. Data and authorization rules still hold during retries and partial failures. Check performance limits, monitoring, recovery, and rollback. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Where the code runs, data stores, traffic shape, consistency needs, and the security boundary. Also confirm the compatibility period, service goals, and rollback limits.

Check this request

Review the current use of Redirect. Definition: A Redirect sends a client from one address to another. Its status says whether the move is temporary or permanent. Release checks: Check contracts and invariants, authorization, and input limits. Test retries, one-time effects, timeouts, and partial failures. Verify data integrity, compatibility, monitoring, recovery, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.

A1
How official is this term?

Official standard

A named standard sets the rules described on this page.

The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example.

Scope
HTTP
Document status
standards track
Checked on
2026-07-30

Evidence sources & scope

Authority source + Term reference · IETF · standards track HTTP Semantics — 15.4 Redirection 3xx 15.4 Redirection 3xx Scope: HTTP; direct scope: 15.4 Redirection 3xx Role here: Direct term reference Source covers: canonical name, definition, semantics, implementation Authority source · IETF · standards track HTTP Semantics Scope: HTTP Role here: Authority within stated scope Source covers: canonical name, definition, semantics, implementation

Copy it yourself

The browser could not copy this. Select the request below and copy it yourself.