Browse Prior Art Database

A Distributed System for Updating Web Content's HTTP Expirations

IP.com Disclosure Number: IPCOM000011311D
Original Publication Date: 2003-Feb-13
Included in the Prior Art Database: 2003-Feb-13
Document File: 2 page(s) / 6K

Publishing Venue

IBM

Abstract

A solution is disclosed that is capable of setting expirations on all content served from a webserver. It provides this setting in a manner which allows for the dynamic update of the expiration data via a networked system of webservers and expiration servers. This does not require a restart of reload of the webserver. It also provides for the potential lack of rules being available by introducing a set of default rules which will be applied to all content if no other rules exist.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 2

A Distributed System for Updating Web Content's HTTP Expirations

A solution is disclosed that is capable of setting expirations on all content served from a webserver. It provides this setting in a manner which allows for the dynamic update of the expiration data via a networked system of webservers and expiration servers. This does not require a restart of reload of the webserver. It also provides for the potential lack of rules being available by introducing a set of default rules which will be applied to all content if no other rules exist.

As the internet continues to grow, it has become more and more important for network infrastructure owners to add HTTP caching servers. These servers exist at several points between a content provider and the content consumer : in the consumer's browser cache, at the consumer's internet service provider, potentially at peering points between the consumer's internet service provider and the provider's network, and in front of the provider's actual webservers. As this practice has grown, it has become necessary for distributors of content which is time-sensitive or rapidly changing to ensure that these caching servers only hold onto content for a limited period of time.

As the internet continues to grow, it has become more and more important for network infrastructure owners to add HTTP caching servers. These servers exist at several points between a content provider and the content consumer: in the consumer's browser cache, at the consumer's internet service provider, potentially at peering points between the consumer's internet service provider and the provider's network, and in front of the provider's actual webservers. As this practice has grown, it has become necessary for distributors of content which is time-sensitive or rapidly changing to ensure that these caching servers only hold onto content for a limited period of time.

HTTP 1.1 provides an extensive set of directives which determine the cacheability of web content. The manipulation of these directives is what allows a content provider to ensure that timely content is received by the consumer as the provider intends. Most webservers allow a server administrator or content publisher to set these directives (headers) on outgoing content. However, as sites grow in size and complexity, it will become necessary to provide a finer-grained control of web content expirations.

This system introduces the following:

1) a custom webserver plugin which hooks into existing webserver API...