RFC 7234

E60792

HTTP specification IETF Request for Comments technical standard

RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

AI illustration

All labels observed (4)

Label	Occurrences
RFC 7234 canonical	9
Cache-Control (HTTP header)	1
Cache-Control header field semantics	1
HTTP caching specifications	1

How this entity was disambiguated

This entity first appeared as the object of triple T471959 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: RFC 7234
Context triple: [HTTP/1.1, definedIn, RFC 7234]

A. RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
B. RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
C. RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
D. RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
E. RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: RFC 7234
Target entity description: RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.

A. RFC 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
B. RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
C. RFC 7235
RFC 7235 is an IETF specification that defined the HTTP/1.1 authentication framework, including the use of challenge-response mechanisms like Basic and Digest authentication.
D. RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
E. RFC 7541
RFC 7541 is the IETF specification that defines the HPACK header compression format used by HTTP/2 to efficiently encode HTTP header fields.
F. None of above. chosen

Statements (44)

Predicate	Object
instanceOf	HTTP specification ⓘ IETF Request for Comments ⓘ technical standard ⓘ
appliesTo	HTTP caches ⓘ HTTP intermediaries ⓘ HTTP/1.1 ⓘ
category	Standards Track ⓘ
defines	Age header field semantics ⓘ Cache-Control header field semantics ⓘ linked to: RFC 7234 ETag-based cache validation semantics ⓘ Expires header field semantics ⓘ HTTP/1.1 caching semantics ⓘ Last-Modified-based cache validation semantics ⓘ cache invalidation rules ⓘ freshness model for HTTP responses ⓘ heuristic caching rules ⓘ requirements for intermediaries acting as HTTP caches ⓘ revalidation mechanisms for HTTP caches ⓘ rules for reusing cached HTTP responses ⓘ rules for storing HTTP responses in caches ⓘ rules for validating cached HTTP responses ⓘ semantics of HTTP caches ⓘ shared vs private cache behavior ⓘ
format	text ⓘ
governs	how HTTP responses may be reused by caches ⓘ how HTTP responses may be stored by caches ⓘ how HTTP responses may be validated by caches ⓘ
isPartOf	RFC 7230–RFC 7235 HTTP/1.1 core specifications ⓘ linked to: RFC 7230
language	English ⓘ
obsoletes	RFC 2616 (caching-related parts) ⓘ linked to: RFC 7232
partOf	HTTP/1.1 specification suite ⓘ linked to: HTTP/1.1
protocol	Hypertext Transfer Protocol ⓘ linked to: HTTP
protocolVersion	HTTP/1.1 ⓘ
publishedBy	IETF ⓘ linked to: Internet Engineering Task Force Internet Engineering Task Force ⓘ
standardizes	behavior of HTTP caches on the Internet ⓘ
status	Internet Standard (via HTTP core update, superseded by RFC 9111) ⓘ linked to: RFC 9111
stream	IETF ⓘ linked to: Internet Engineering Task Force
subject	HTTP intermediaries ⓘ HTTP performance ⓘ web caching ⓘ
supersededBy	RFC 9111 ⓘ
title	Hypertext Transfer Protocol (HTTP/1.1): Caching ⓘ linked to: HTTP Caching
updates	HTTP/1.1 caching semantics ⓘ linked to: HTTP Caching

How these facts were elicited

Referenced by (12)

Full triples — surface form annotated when it differs from this entity's canonical label.

HTTP/1.1 → definedIn → RFC 7234 ⓘ

HTTP Caching → definedIn → RFC 7234 ⓘ

RFC 7232 → relatedTo → RFC 7234 ⓘ

RFC 9110 → replaces → RFC 7234 ⓘ

RFC 9110 → obsoletes → RFC 7234 ⓘ

RFC 7233 → relatedTo → RFC 7234 ⓘ

RFC 7230 → relatedTo → RFC 7234 ⓘ

HTTP Working Group → responsibleFor → HTTP caching specifications ⓘ

linked to: RFC 7234

RFC 7234 → defines → Cache-Control header field semantics ⓘ

linked to: RFC 7234

Date (HTTP header) → relatedTo → Cache-Control (HTTP header) ⓘ

subject linked to: Date

linked to: RFC 7234

RFC 2616 → obsoletedBy → RFC 7234 ⓘ

Age (HTTP header) → definedIn → RFC 7234 ⓘ

All labels observed (4)

How this entity was disambiguated Show

Statements (44)

How these facts were elicited Show

Referenced by (12)

How this entity was disambiguated

How these facts were elicited