HTTP Caching
E35276
HTTP Caching is the standardized mechanism in the HTTP protocol that defines how responses can be stored and reused to improve web performance, reduce latency, and decrease network load.
All labels observed (6)
| Label | Occurrences |
|---|---|
| AMP caches | 1 |
| Cache-Control (HTTP header) | 1 |
| HTTP Caching canonical | 1 |
| HTTP caching semantics | 1 |
| HTTP/1.1 caching semantics | 1 |
| Hypertext Transfer Protocol (HTTP/1.1): Caching | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T270876 — 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: HTTP Caching Context triple: [RFC 9111, title, HTTP Caching]
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
AJAX
AJAX is a web development technique that allows web pages to update content asynchronously by exchanging data with a server in the background without reloading the entire page.
-
E.
HTTP/1.1
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
- 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: HTTP Caching Target entity description: HTTP Caching is the standardized mechanism in the HTTP protocol that defines how responses can be stored and reused to improve web performance, reduce latency, and decrease network load.
-
A.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
-
B.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
C.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
D.
AJAX
AJAX is a web development technique that allows web pages to update content asynchronously by exchanging data with a server in the background without reloading the entire page.
-
E.
HTTP/1.1
HTTP/1.1 is a widely used version of the Hypertext Transfer Protocol that introduced persistent connections, chunked transfer encoding, and improved caching mechanisms for web communication.
- F. None of above. chosen
Statements (80)
| Predicate | Object |
|---|---|
| instanceOf |
Caching mechanism
ⓘ
HTTP mechanism ⓘ Web technology ⓘ |
| appliesTo |
HTTP requests
ⓘ
HTTP responses ⓘ |
| canBeBypassedBy |
Authorization headers
ⓘ
Cache-busting URLs ⓘ no-store directive ⓘ |
| constrainedBy |
Cache-control directives from origin
ⓘ
Privacy requirements ⓘ Security requirements ⓘ |
| definedIn |
HTTP/1.1 specification
ⓘ
RFC 7234 ⓘ RFC 9111 ⓘ |
| determines |
How long a response stays fresh
ⓘ
When a cached response must be revalidated ⓘ Whether a response is cacheable ⓘ |
| hasEffect |
Enables offline or limited-connectivity usage
ⓘ
Improves perceived page load time ⓘ Reduces repeated data transfer ⓘ |
| hasPurpose |
Decrease network load
ⓘ
Enable reuse of HTTP responses ⓘ Improve web performance ⓘ Reduce latency ⓘ Reduce server load ⓘ |
| involvesActor |
Browser
ⓘ
Content delivery network ⓘ Origin server ⓘ Proxy cache ⓘ User agent ⓘ |
| partOf |
Hypertext Transfer Protocol
ⓘ
linked to:
HTTP
|
| relatedTo |
Content negotiation
ⓘ
HTTP performance optimization ⓘ Web scalability ⓘ |
| supports |
Conditional GET requests
ⓘ
Conditional HEAD requests ⓘ |
| usedBy |
CDN edge servers
ⓘ
Forward proxies ⓘ Reverse proxies ⓘ Web browsers ⓘ |
| usesConcept |
Cache invalidation
ⓘ
Cache key ⓘ Cache validator ⓘ Cacheable response ⓘ Conditional request ⓘ End-to-end revalidation ⓘ Expiration ⓘ Freshness ⓘ Freshness lifetime ⓘ Heuristic caching ⓘ Intermediate cache ⓘ Private cache ⓘ Revalidation ⓘ Shared cache ⓘ Stale response ⓘ Validation ⓘ Varying by request header ⓘ |
| usesDirective |
immutable
ⓘ
max-age ⓘ must-revalidate ⓘ no-cache ⓘ no-store ⓘ private ⓘ proxy-revalidate ⓘ public ⓘ s-maxage ⓘ stale-if-error ⓘ stale-while-revalidate ⓘ |
| usesHeader |
Age
ⓘ
Cache-Control ⓘ ETag ⓘ Expires ⓘ If-Match ⓘ If-Modified-Since ⓘ If-None-Match ⓘ If-Unmodified-Since ⓘ Last-Modified ⓘ Pragma ⓘ Vary ⓘ Warning ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: HTTP Caching Description of subject: HTTP Caching is the standardized mechanism in the HTTP protocol that defines how responses can be stored and reused to improve web performance, reduce latency, and decrease network load.
Referenced by (6)
Full triples — surface form annotated when it differs from this entity's canonical label.
subject linked to:
AMP (as a collaborating project)
linked to: HTTP Caching
linked to: HTTP Caching