Cloudflare, Inc.

Cloudfare, Inc.

Alex Krivit

Samantha Aki Shugaeva

Connor Harwood

Rustam Xing Lalkaka

Yuchen Wu

Zaidoon Abd Al Hadi

Edward H Wang

Steven Alexander Siloti

Young Keun Park

Matthew Gumport

Syed Suleman Ahmad

Anthony Raymond Rabia Seure

Avani Gadani

William Woodhead

Thomas Hatzopoulos

Jee Hoon Kim

Automatic speculation configuration management is described. An intermediary server receives a request from a client. The resource is retrieved from the origin server, where the resource includes link(s) to other resource(s). The intermediary server generates and transmits a response that includes a header that references a speculation configuration for prefetching at least one of the other resource(s). The intermediary server receives a request for the speculation configuration from the client. The intermediary server generates and transmits a response to the client that includes the speculation configuration. The intermediary server receives a prefetching request from the client for one of the resources indicated in the speculation configuration, retrieves that resource, and transmits a response to the client with that resource.

Automatic speculation configuration management

Purging resources from a cache in a distributed networked system is described. A compute server of a first data center of the distributed networked system receives a purge request to purge a resource from cache. If the purge request does not include a cache key, the compute server determines whether the purge request is valid, and if valid, purges the resource from cache of the first data center, generates a cache key for the resource, and causes the purge request that includes the generated cache key to be sent to other data centers of the distributed networked system for purging the resource from cache. If the purge request includes a cache key, the compute server skips determining whether the purge request is valid and purges the resource from cache based on the cache key.

Cache purging in a distributed networked system

An intermediary server receives a request from a client that identifies an asset that is handled by an origin server. The intermediary server generates an informational response that includes one or more link header fields that reference one or more pieces of content respectively that are predicted by the intermediary server to be linked within a final response for the asset. The intermediary server transmits the generated informational response to the client prior to a final response for the request. The intermediary server transmits the request to the origin server and receives a final response to the request. The intermediary server transmits the final response to the request to the client.

Generating early hints informational responses at an intermediary server

Purging resources from a cache in a distributed networked system is described. A first data center of the distributed networked system receives a purge request to purge a resource from cache. If the purge request does not include a cache key, the first data center determines whether the purge request is valid, and if valid, purges the resource from cache of the first data center, generates a cache key for the resource, and causes the purge request that includes the generated cache key to be sent to other data centers of the distributed networked system for purging the resource from cache. If the purge request includes a cache key, the first data center skips determining whether the purge request is valid and purges the resource from cache based on the cache key.

An intermediary server determines, for an asset handled by an origin server, piece(s) of content for inclusion in link header field(s) in an informational response that signifies that the piece(s) of content are predicted to be linked within a final response for the asset. The intermediary server generates an informational response that includes the link header field(s) and responds to a request from a client with the informational response. The intermediary server transmits the request to the origin server. The intermediary server receives the final response to the request from the origin server, and transmits the final response to the client.

Growing community of inventors

Edwards, CO, United States of America

Alex Krivit