Meaning
Standardized numeric codes returned by an HTTP server to indicate the outcome of an HTTP request.
Primary Function
Communicate the result of an HTTP request (success, redirection, client error, server error) to the client.
Communicative Purpose
Convey the outcome of an HTTP interaction using a standardized three-digit code and optional reason phrase.
Pattern
three-digit numeric code
Core Structure
three-digit number
Função primária
Communicate the result of an HTTP request (success, redirection, client error, server error) to the client.
Propósito comunicativo
Convey the outcome of an HTTP interaction using a standardized three-digit code and optional reason phrase.
Situações de gatilho
When an HTTP client receives a response from a server; when debugging HTTP interactions; when designing RESTful APIs.
Contextos
Web development, API design, network debugging, HTTP protocol specifications, troubleshooting.
Padrão
three-digit numeric code
Estrutura central
three-digit number
Slots de substituição
none
Colocados típicos
- 200 OK
- 404 Not Found
- 500 Internal Server Error
- 301 Moved Permanently
Substituições comuns
- none
Erros comuns
Confusing similar codes (e.g., 401 vs 403), assuming reason phrase is standardized.
Similar / contraste
HTTP methods (GET, POST), MIME types, WebSocket status codes.
Interferências
Confusing with FTP or SMTP status codes.
Família do chunk
- HTTP protocol concepts
- REST API design
- Web protocols
Nuance
The reason phrase is advisory; only the numeric code is semantically binding.
Efeito pragmático
Conveys the outcome of an HTTP request, enabling clients to decide subsequent actions (e.g., retry, display error).
Dica de memória
Think of a web browser showing a status code when a page fails to load.
Nota
Only the numeric part of the status line is standardized; the reason phrase is advisory and may differ across implementations.
Upgrade path
Learn about HTTP response headers and RESTful status code conventions.
Log in to save chunks.