01
Search by the token you already have
The same field accepts GET, Content-Type, application/json and .webp. An extension search is a lookup, not a content detector.
Developer reference
HTTP referencefor everyday protocol questions
Search a method, header name, media type or common extension in one local index.
HTTP reference
Matches
Content-Type
HeadersMeaning: Identifies the media type of the current request or response body.
Direction: Both
Watch out: Content-Type labels the current representation. Charset and multipart boundary parameters have separate rules.
HTTP example
Content-Type: application/jsonQueries stay in this page; external sources open only when you choose a link.
Category
2 of 46 curated entries
IANA methods · 17 Jun 2026; fields · 28 Aug 2026Entries checked 23 Sep 2026
When an API behaves unexpectedly, an HTTP reference helps separate method semantics from header fields and body media types. Try Content-Type, GET or .webp without sending a request.
This HTTP reference connects each selected token to a concrete HTTP example and its source. Use the IANA links when an extension, a new method or a service-specific value needs closer checking.
Why use this HTTP reference
The nearby concepts stay connected without pretending the index is exhaustive.
Follow a header to its body type
Content-Type describes the representation, while Accept describes a client preference. This HTTP reference puts an actual header line next to the media type it names.
Check a type without trusting the filename
Search .webp to find image/webp, then read the note that an extension is only a common association. The HTTP reference does not inspect file bytes.
Three checks before copying a protocol example
02
Read the field that changes meaning
Methods show safe and idempotent separately; headers show request or response direction; media types show common extensions rather than guaranteed file formats.
03
Open the source for edge cases
The source link points to a specification or MDN entry. QUERY is registered, but your target server must still support it before you use it.
One lookup across three HTTP layers
Methods with semantics
The method cards include GET through QUERY with safety, idempotence and a sample request; QUERY links to RFC 10008.
Headers with direction
Selected HTTP headers show whether they occur in requests, responses or both, alongside a concrete field value.
Media types with examples
MIME types show a Content-Type line and common extensions; image/webp and text/javascript reflect current registered names.
Where the quick reference stops
- A selected index, not every registration
- This HTTP reference contains 46 selected entries. A missing method, header or MIME type is outside this set, not necessarily invalid; use the full IANA registry.
- No request is sent
- The example method lines are text. The page does not fetch a URL or test whether an endpoint implements QUERY, TRACE or any other method.
- Extensions do not verify bytes
- Searching .webp retrieves a likely media type, but filenames can be renamed and one extension can have several suitable types. Inspect the actual content when correctness matters.
- Status codes and parsing live elsewhere
- This reference does not interpret a raw header block or define response status codes. Open the dedicated header parser when you need to analyze real input.
HTTP reference questions
What is the difference between PUT, POST, and PATCH?
PUT replaces a target representation and is idempotent; PATCH applies a partial change and is not inherently idempotent. POST asks the target to process content. Check the method cards and your API contract.
What is the difference between the Accept and Content-Type HTTP headers?
Accept lists response types the client can accept. Content-Type states the media type of the body in the current request or response; they can legitimately differ.
Is PATCH idempotent?
No general guarantee. A particular PATCH document may be written idempotently, but the method registry does not promise that repeated PATCH requests have the same effect.
Does a file extension determine its MIME type?
No. The extension lookup offers a common association only. A server must send an appropriate Content-Type, and actual file bytes may differ from the filename.
When should I use HEAD instead of GET?
HEAD asks for metadata corresponding to GET without a response body. It is useful when you need headers such as Content-Length before deciding whether to fetch the representation.
Missing a token or found a mistake?
Use the HTTP reference now
Look up a token, read its example and boundary, then follow the primary source for production decisions.