What is the difference between the glossary and the long-form guides?
The glossary tells you what a term means. The guides show how those terms interact in real requests, browser behavior, API design, and debugging work.
Definitions
HTTP Glossary
Use this when you know the term you are seeing in docs, DevTools, or a code review, but want the plain HTTP meaning quickly.
HTTP Cookie
Learn what HTTP cookies are and how browsers store small data pieces for websites. Understand cookie attributes, security, and session management.
HTTP Error Handling
Learn HTTP error handling best practices for detecting, managing, and responding to errors gracefully. Understand status codes, retry logic, and user feedback.
HTTP Header
Learn what HTTP headers are and how they provide metadata about requests and responses. Understand common headers like Content-Type and Authorization.
HTTP Method
Learn what HTTP methods are and how they define actions on resources. Understand GET, POST, PUT, DELETE, PATCH, and other methods with examples.
HTTP Payload
Learn what HTTP payload means and how message bodies carry data in requests and responses. Understand JSON, form data, and binary payloads.
HTTP Request
Learn what an HTTP request is and how clients send messages to servers. Understand request structure, methods, headers, and body components.
HTTP Response
Learn what an HTTP response is and how servers reply to client requests. Understand response structure, status codes, headers, and body content.
HTTP Session
Learn what HTTP sessions are and how they maintain state across stateless HTTP requests. Understand session cookies, tokens, and server-side storage.
HTTP Status Code
Learn what HTTP status codes are and how they indicate request results. Understand 1xx, 2xx, 3xx, 4xx, and 5xx code classes with common examples.
Idempotent
Learn what idempotent means in HTTP. Understand why GET, PUT, and DELETE are idempotent, why POST is not, and how idempotency affects API design.
What This Glossary Is For
Use the glossary when you know the term but want the protocol meaning, not a framework-specific shortcut. It is the fastest way to get oriented before diving into a guide, a bug, or a tooling readout.
- Read a glossary page first when two teams are using the same word differently.
- Jump to a guide when the term is clear but the implementation tradeoffs are not.
- Use these definitions as the shared vocabulary for methods, headers, status codes, and cookies.
Good Places To Start
If you are new to HTTP terminology, these pages cover the terms that unlock the rest of the site fastest.
- HTTP Cookie
- Learn what HTTP cookies are and how browsers store small data pieces for websites. Understand cookie attributes, security, and session management.
- HTTP Error Handling
- Learn HTTP error handling best practices for detecting, managing, and responding to errors gracefully. Understand status codes, retry logic, and user feedback.
- HTTP Header
- Learn what HTTP headers are and how they provide metadata about requests and responses. Understand common headers like Content-Type and Authorization.
- HTTP Method
- Learn what HTTP methods are and how they define actions on resources. Understand GET, POST, PUT, DELETE, PATCH, and other methods with examples.
- HTTP Payload
- Learn what HTTP payload means and how message bodies carry data in requests and responses. Understand JSON, form data, and binary payloads.
- HTTP Request
- Learn what an HTTP request is and how clients send messages to servers. Understand request structure, methods, headers, and body components.
Good Questions To Start With
When should I use the glossary instead of search?
Use the glossary when you already know the word but want the exact meaning. Use search when you know the symptom or task, but not the HTTP term behind it.
Why do terms like request, response, and header get separate pages?
Because they are related but not interchangeable. Keeping them separate makes the definitions tighter and helps you move from a vague mental model to the exact protocol concept you need.