Method and apparatus for maintaining state information on an HTTP client system in relation to server domain and path attributes

This application is a divisional of U.S. patent application Ser. No. 08/540,342, filed Oct. 6, 1995, which is now U.S. Pat. No. 5,774,670, which issued on Jun. 30,1998.

id="REI-00002" date="20111101"

CROSS REFERENCE TO RELATED APPLICATIONS

id="REI-00002"

This application is a reissue application of U.S. Pat. No. 6,134,592 granted Oct. 17, 2000 (application Ser. No. 08/918,977 filed Aug. 27, 1997), which is a divisional of U.S. Pat. No. 5,774,670 granted Jun. 30, 1998 (application Ser. No. 08/540,342, filed Oct. 6, 1995). Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 6,134,592. The reissue applications of U.S. Pat. No. 6,134,592 are U.S. patent application Ser. No. 10/272,896 (the present application), as well as its divisional reissue applications including U.S. patent application Ser. Nos. 11/737,043, 11/737,042 and 11/737,055 all of which were filed on Apr. 18, 2007.

FIELD OF THE INVENTION

This invention relates to communication in a client-server computer systems. Specifically, the invention relates to client-server computer systems in which a server can send state information to a client and the client stores the state information for later retransmissions back to the server.

BACKGROUND OF THE INVENTION

An important use of computers is the transfer of information over a network. Currently, the largest computer network in existence is the InterNet. The InterNet is a worldwide interconnection of computer networks that communicate using a common protocol. Millions of computers, from low end personal computers to high-end super computers are coupled to the InterNet.

The InterNet grew out of work funded in the 1960s by the U.S. Defense Department's Advanced Research Projects Agency. For a long time, InterNet was used by researchers in universities and national laboratories to share information. As the existence of the InterNet became more widely known, many users outside of the academic/research community (e.g., employees of large corporations) started to use InterNet to carry electronic mail.

In 1989, a new type of information system known as the World-Wide-Web (“the Web”) was introduced to the InterNet. Early development of the Web took place at CERN, the European Particle Physics Laboratory. The Web is a wide-area hypermedia information retrieval system aimed to give wide access to a large universe of documents. At that time, the Web was known to and used by the academic/research community only. There was no easily available tool which allows a technically untrained person to access the Web.

In 1993, researchers at the National Center for Supercomputing Applications (NCSA) released a Web browser called “Mosiac” that implemented a graphical user interface (GUI). Mosiac's graphical user interface was simple to learn yet powerful. The Mosiac browser allows a user to retrieve documents from the World-Wide-Web using simple point-and-click commands. Because the user does not have to be technically trained and the browser is pleasant to use, it has the potential of opening up the InterNet to the masses.

The architecture of the Web follows a conventional client-server model. The terms “client” and “server” are used to refer to a computer's general role as a requester of data (the client) or provider of data (the server). Under the Web environment, Web browsers reside in clients and Web documents reside in servers. Web clients and Web servers communicate using a protocol called “HyperText Transfer Protocol” (HTTP). A browser opens a connection to a server and initiates a request for a document. The server delivers the requested document, typically in the form of a text document coded in a standard Hypertext Markup Language (HTML) format, and when the connection is closed in the above interaction, the server serves a passive role, i.e., it accepts commands from the client and cannot request the client to perform any action.

The communication model under the conventional Web environment provides a very limited level of interaction between clients and servers. In many systems, increasing the level of interaction between components in the systems often makes the systems more robust, but increasing the interaction increases the complexity of the interaction and typically slows the rate of the interaction. Thus, the conventional Web environment provides less complex, faster interactions because of the Web's level of interaction between clients and servers.

In the conventional Web environment, clients do not retain information of a session after the session is closed. In many systems, the ability to retain information after the systems become inactive is crucial to the functioning of the systems. Thus, it is desirable to allow clients to have this ability.

SUMMARY OF THE INVENTION

The present invention involves a client-server system on a network in which a server can send state information to a client and the client stores the state information. The stored state information can later be sent back to the server at appropriate times. In this manner, the state of a client can be maintained in the client-server system where no state inherently exists in such a system.

One embodiment of the present invention is a network system for communicating documents containing information such as text and one or more images. The system comprises a first computer (i.e., a server) capable of sending such documents over a network such as the InterNet. The system also has a second computer (i.e., a client) which can request these documents or files from the server. After the requested documents are received, the client can display the documents. In accordance with the present invention, the server can send state information to the client when a document is sent. The client then stores the state information, which is typically in the form of a state object. In a subsequent request for documents to the server, the client can send the stored state information to the server.

In an embodiment of the invention, the server uses a hypertext transfer protocol (“http”) to communicate over the network with clients; such clients also communicate with the server using the hypertext transfer protocol. This server and these clients are referred to as an http server and http clients respectively. The server typically will include a server processor and a memory and a computer readable medium, such as a magnetic (“hard disk”) or optical mass storage device, and the computer readable medium of the server contains computer program instructions for transmitting the file from the server system to the client system and for transmitting the state object to the client system. The client typically will include a client processor and a memory and a computer readable medium, such as a magnetic or optical mass storage device, and the computer readable medium of the client contains computer program instructions for receiving the state object, which specifies the state information, from the server and for storing the state object at the client. The state object, in a typical embodiment, will include a name attribute, such as a domain attribute.

One of the applications of the present invention is an on-line shopping system. A customer can browse information delivered by a merchant server using a browser running on a client. The customer can also select products to be placed in a virtual shopping basket. The server then sends state information related to the selected products to the browser on the client for storage. When the customer wants to purchase the products in the virtual shopping basket, the browser sends the corresponding state information to a specified check-out Web page for processing.

Another application of the present invention is an “on-line” information service, such as a newspaper's Web server which includes articles or other information from the newspaper's subscription services. In one example, a newspaper or publishing company may have several different publications, each requiring a separate subscription fee which may differ among the different publications. A user of the information service may browse the different publications by making http requests, from the client's/user's computer system, to the publisher's Web server which responds with the requested publication and state information specifying the user's identification, and other subscription information (e.g., user registration and billing information) which allows the user to view the contents of the publication; this information is typically provided by the user at least once in a conventional log-on process. Thereafter, this information is included in the state information which is exchanged between the client and the server in the process of the invention. Accordingly, when the user, during the browsing process, desires to view another publication (e.g., from the same or different publisher) this state information will be transmitted back to the Web server to provide the necessary subscription information (thereby entitling the user to view the publication) without requiring the user to re-enter the necessary subscription information. In this manner, a user may browse from publication to publication on the Web server or a different Web server in the domain without having to re-enter, when seeking a new publication, the necessary subscription information.

These and other features of the present invention will be disclosed in the following description of the invention together with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects, features, and advantages of the present invention will be apparent from the following detailed description of the preferred embodiment of the invention with references to the following drawings.

<figref idref="DRAWINGS">FIG. 1A</figref> is a pictorial diagram of a computer network used in the present invention.

<figref idref="DRAWINGS">FIG. 1B</figref> shows a computer network containing a client system and a server system.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates the retrieval of remote text and images and their integration in a document.

<figref idref="DRAWINGS">FIG. 3A</figref> shows an example of an HTML document which can be processed by the browser of the present invention.

<figref idref="DRAWINGS">FIG. 3B</figref> shows the integrated document corresponding to the HTML document of <figref idref="DRAWINGS">FIG. 3A</figref> as it would appear on a display screen of a client computer.

<figref idref="DRAWINGS">FIG. 4</figref> shows schematically the flow of information between a client and a server in accordance with the present invention.

<figref idref="DRAWINGS">FIG. 5</figref> is a flow chart showing the operation of a merchant system of the present invention.

<figref idref="DRAWINGS">FIG. 6</figref> shows a computer system that could be used to run the browser of the present invention.

DETAILED DESCRIPTION

Methods and apparatuses for maintaining state information in a client-server based computer network system are disclosed. The following description is presented to enable any person skilled in the art to make and use the invention. For purposes of explanation, specific nomenclature is set forth to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that these specific details are not required to practice the present invention. Descriptions of specific applications are provided only as examples. Various modifications to the preferred embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

Prior to describing the present invention, some introductory material is explained, including explanations concerning client-server computing, InterNet addresses, URL's and browsing of the Web.

Client-Server Computing

<figref idref="DRAWINGS">FIG. 1A</figref> illustrates a conceptual diagram of a computer network <b>100</b>, such as the InterNet. Computer network <b>100</b> comprises small computers (such as computers <b>102</b>, <b>104</b>, <b>106</b>, <b>108</b>, <b>110</b> and <b>112</b>) and large computers, such as computers A and B, commonly used as servers. In general, small computers are “personal computers” or workstations and are the sites at which a human user operates the computer to make requests for data from other computers or servers on the network. Usually, the requested data resides in large computers. In this scenario, small computers are clients and the large computers are servers. In this specification, the terms “client” and “server” are used to refer to a computer's general role as a requester of data (client) or provider of data (server). In general, the size of a computer or the resources associated with it do not preclude the computer's ability to act as a client or a server. Further, each computer may request data in one transaction and provide data in another transaction, thus changing the computer's role from client to server, or vice versa.

A client, such as computer <b>102</b>, may request a file from server A. Since computer <b>102</b> is directly connected to server A through a local area network, this request would not normally result in a transfer of data over what is shown as the “network” of <figref idref="DRAWINGS">FIG. 1</figref>. The “network” of <figref idref="DRAWINGS">FIG. 1</figref> represents the InterNet which is an interconnection of networks. A different request from computer <b>102</b> may be for a file that resides in server B. In this case, the data is transferred from server B through the network to server A and, finally, to computer <b>102</b>. The distance between servers A and B may be very long, e.g. across continents, or very short, e.g., within the same city. Further, in traversing the network the data may be transferred through several intermediate servers and many routing devices, such as bridges and routers.

The World-Wide-Web (“The Web”) uses the client-server model to communicate information between clients and servers. Web Servers are coupled to the InterNet and respond to document requests from Web clients. Web clients (also known as Web “browsers”) are programs that allow a user to simply access Web documents located on Web Servers.

<figref idref="DRAWINGS">FIG. 1B</figref> shows, in more detail, an example of a client-server system interconnected through the InterNet <b>100</b>. In this example, a remote server system <b>122</b> is interconnected through the InterNet to client system <b>120</b>. The client system <b>120</b> includes conventional components such as a processor <b>124</b>, memory <b>125</b> (e.g. RAM), a bus <b>126</b> which couples the processor <b>124</b> and memory <b>125</b>, a mass storage device <b>127</b> (e.g. a magnetic hard disk or an optical storage disk) coupled to the processor and memory through an I/O controller <b>128</b> and a network interface <b>129</b>, such as a conventional modem. The server system <b>122</b> also includes conventional components such as a processor <b>134</b>, memory <b>135</b> (e.g. RAM), a bus <b>136</b> which couples the processor <b>134</b> and memory <b>135</b>, a mass storage device <b>137</b> (e.g. a magnetic or optical disk) coupled to the processor <b>134</b> and memory <b>135</b> through an I/O controller <b>138</b> and a network interface <b>139</b>, such as a conventional modem. It will be appreciated from the description below that the present invention may be implemented in software which is stored as executable instructions on a computer readable medium on the client and server systems, such as mass storage devices <b>127</b> and <b>137</b> respectively, or in memories <b>125</b> and <b>135</b> respectively.

InterNet Addresses

As discussed in the background, the InterNet consists of a worldwide computer network that communicates using well defined protocol known as the InterNet Protocol (IP). Computer systems that are directly connected to the InterNet each have an unique InterNet address. An InterNet address consists of four numbers where each number is less than 256. The four numbers of an InterNet address are commonly written out separated by periods such as 192.101.0.3

To simplify InterNet addressing, the “Domain Name System” was created. The domain name system allows users to access InterNet resources with a simpler alphanumeric naming system. An InterNet Domain name consists of a series of alphanumeric names separated by periods. For example, the name “drizzle.stanford.edu” is the name for a computer in the physics department at Stanford University. Read from left to right, each name defines a subset of the name immediately to the right. In this example, “drizzle” is the name of a workstation in the “stanford” domain. Furthermore, “stanford” is a subset of the “edu” domain. When a domain name is used, the computer accesses a “Domain Name Server” to obtain the explicit four number InterNet address.

Uniform Resource Locators

To further define the addresses of resources on the InterNet, the Uniform Resource Locator system was created. A Uniform Resource Locator (URL) is a descriptor that specifically defines a type of InterNet resource and its location. URLs have the following format: <ul id="ul0001" list-style="none"><li id="ul0001-0001" num="0000"><ul id="ul0002" list-style="none"><li id="ul0002-0001" num="0035">resource_type://domain.address/path_name <br /> Where “resource_type” defines the type of internet resource. Web documents are identified by the resource type “http” which indicates that the hypertext transfer protocol should be used to access the document. Other resource types include “ftp” (file transmission protocol) and “telnet”. The “domain.address” defines the domain name address of the computer that the /resource is located on. Finally, the “path_name” defines a directory path within the file system of the server that identifies the resource. The right most name on the path name portion is usually the name of an actual file. Web pages are identified by the resource type “http”. By convention, most Web pages end with the suffix “.html” that suggests the file is a HyperText Markup Language document. </li></ul></li></ul>

An example of a URL for a Web document is: <ul id="ul0003" list-style="none"><li id="ul0003-0001" num="0000"><ul id="ul0004" list-style="none"><li id="ul0004-0001" num="0037">http://info.cern.ch/hypertext/Datasources/WWW/Geographical.html <br /> This URL indicates that by using the HTTP (Web) protocol to reach a server called “info.cern.ch”, there is a directory “hypertext/Datasources/WWW” that contains a hypertext document named “Geographical.html.” Resources on the Internet are uniquely addressable by their URL. </li></ul></li></ul>

Browsing the World-Wide-Web

To access an initial Web document, the user enters the URL for a Web document into a Web browser program. The Web browser then sends an http request to the server that has the Web document using the URL. The Web server responds to the http request by sending the requested HTTP object to the client. In most cases, the HTTP object is an plain text (ASCII) document containing text (in ASCII) that is written in HyperText Markup Language (HTML). The HTML document usually contains hyperlinks to other Web documents. The Web browser displays the HTML document on the screen for the user and the hyperlinks to other Web documents are emphasized in some fashion such that the user can selected the hyperlink.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates the retrieval of remote text and images and their integration in a Web page by a client computer <b>130</b>. In <figref idref="DRAWINGS">FIG. 2</figref>, server A contains a text document coded in a standard HTML format. Server B contains an image file called Image <b>1</b> and server C contains another image file called Image <b>2</b>. Each of these servers is remotely located from the other servers and the client <b>130</b>. The transfer of data is via the Internet. It should be appreciated that the text and image files could be located in the same server which is remote from client <b>130</b>.

<figref idref="DRAWINGS">FIG. 3A</figref> shows an example of an HTML document. <figref idref="DRAWINGS">FIG. 3B</figref> shows the corresponding integrated document (Web page) as it would appear on a display screen of a client computer. The first line of the document in <figref idref="DRAWINGS">FIG. 3A</figref> reads “&lt;title&gt; Distributed Image Loading Example&lt;/title&gt;.” In this case, the tags &lt;title&gt; and &lt;/title&gt; are HTML delimiters corresponding to the beginning and ending, respectively, of text that is designated as the title of the HTML document. The title could be used for various purposes, such as listing of the document in an automatically generated index.

The second line of the HTML document of <figref idref="DRAWINGS">FIG. 3A</figref> reads “&lt;h1&gt; Distributed Image Loading Example &lt;/h1&gt;” The &lt;h1&gt; and &lt;/h1&gt; are HTML delimiters for a header that is to be displayed in a largest font. The browser software running on the client computer <b>130</b> interprets the header tags and thus displays the text between the header tags in a largest font size on the client's display screen.

After the title and header, the HTML document of <figref idref="DRAWINGS">FIG. 3A</figref> contains the text “One of the major features . . . capability”. At the end of the text paragraph is another HTML tag shown as &lt;p&gt;. This is a tag indicating the end of a paragraph.

To continue with the second paragraph of the HTML document, the text reads “This document . . . this image: &lt;IMG align=middle src=“http://www.su.se/SUlogo.gif”&gt; was obtained . . . ”. The text in angle brackets defines an image to be placed in the text. Specifically, the “IMG” tag indicates that an image is being defined. The “align=middle” tag indicates that the image should be aligned in the middle of the current line of text. Finally, “src=” tag indicates that the source image file can be located using the URL “http://www.su.se/SUlogo.gif”.

The line continues with the phrase “from the &lt;A href=“http://www.su.se/index.html”&gt; University of Stockholm&lt;/A&gt; This phrase defines “University of Stockholm” as a link to another Web document. Specifically, the “A” tag defines the beginning of a link. The “href=” tag defines that the link is to a Web page that can be located using the URL “http://www.su.se/index.html” Next, the text “University of Stockholm” is the text that will be the link. Finally, the “/A” tag defines the end of the link definition. As illustrated in <figref idref="DRAWINGS">FIG. 3B</figref>, the text “University of Stockholm” is displayed with underlining that indicates it is a link to another document. If the user selects the underlined text “University of Stockholm”, then the browser will send out a http request for the Web page at the URL address “http://www.su.se/index.html”.

It can be seen from the above example that the HTML document contains all information a browser needs for displaying a Web page. Thus, the only responsibility of a Web server is to provide the requested document, and there is no need for the server to request a client to do anything else. However, this role of a server also limits the utility of the Web environment.

Adding State Information to the HyperText Transfer Protocol

The present invention provides an extension to the prior art HTTP protocol. Using the teachings of the present invention, when a server responds to an http request by returning an HTTP object to a client, the server may also send a piece of state information that the client system will store. In an embodiment of the present invention, the state information is referred to as a “cookie”. Included in the state information (the cookie) is a description of a range of URLs for which that state information should be repeated back to. Thus, when the client system sends future HTTP requests to servers that fall within the range of defined URLs, the requests will include a transmittal of the current value of the state object. By adding the ability to transfer state information back and forth, Web servers can then play an active role in transactions between clients and servers. The term state object is also used herein to refer to the state information.

<figref idref="DRAWINGS">FIG. 4</figref> is a drawing showing schematically the flow of information between a client system and a server system. At a time indicated by numeral <b>172</b>, the client system sends an http request to the Web server. In response to the http request, the server returns an HTML document together with a header, which is typically separate from the HTML documents, at a time indicated by numeral <b>174</b>. The header may contain one or more cookies. Upon receiving the HTML document and the header, the client system displays an HTML document on the screen and stores the cookies in a memory such as a storage medium. The client may switch and work on other tasks, or may be shut down completely. This is indicated by a dash line <b>176</b>. At a time indicated by numeral <b>178</b>, the client system may access a Web server that is specified in the received cookie, such that the client system transmits the cookies to the server, thus providing stale information about the client system to the server system.

This extension to the http protocol provides a powerful new tool which enables a large number of new types of applications to be written for a Web-based environment. Examples of new applications include on-line shopping that stores information about items currently selected by consumers, for-fee on-line services that can send back registration information and thus free users from retyping a user-id on next connection, and Web sites that can store per-user preferences on the client system and have the client supply those preferences every time the site is later accessed.

Server Behavior

A particular embodiment of the state information is described below in order to provide an example according to the present invention. It will be appreciated that alternative formats may be used in accordance with the principles of the present invention. As stated above, the extension to the HTTP protocol adds a new piece of state information to the HTTP header as part of an HTTP response from a Web server. Typically, the state information is generated by a common gateway interface (“CGI”) script. The state information is stored by the receiving client system in the form of a “cookie list” for later use. The syntax of the new data, in one embodiment, is: <ul id="ul0005" list-style="none"><li id="ul0005-0001" num="0000"><ul id="ul0006" list-style="none"><li id="ul0006-0001" num="0050">Set-Cookie: NAME=VALUE; expires=DATE; path=PATH;</li><li id="ul0006-0002" num="0051">domain=DOMAIN_NAME; secure <br /> The capitalized terms can be set by the server system. The first attribute is “NAME=VALUE”. This attribute serves to identify a cookie. The “NAME” attribute is a name for the cookie. The “NAME” attribute is the only required attribute on the “Set-Cookie” header in one embodiment. The “VALUE” is a value assigned to the previously defined name. The “VALUE” is a string of characters excluding, in one embodiment, semicolon, comma, and white spaces. If there is a need to place these characters in the VALUE, standard encoding methods, such as URL's type % XX encoding, can be used. </li></ul></li></ul>

The “expires” attribute specifies a data string that defines the valid life time of the corresponding cookie. Once the expiration date has been reached, the cookie will no longer be stored in the client system. Thus, the client system will no longer respond to Web servers with the cookie. Many coding schemes for designating time can be used. In a preferred embodiment, the “expires” attribute is formatted as: Wdy, DD-Mon-YY HH:MM:SS GMT In the this format, “Wdy” designates the day of a week, “DD-Mon-YY” designates the day, month and year, and “HH:MM:SS GMT” designates the hour, minute and second, in GMT time zone. Note that the “expires” attribute lets a client know when it is safe to purge a cookie, however, the client is not required to delete the cookie. If an expires attribute is not provided by the server, then the cookies expires when the user's session ends. This can be implemented by storing the cookie only in volatile memory.

The “domain=DOMAIN_NAME” attribute defines a domain for which the cookie is valid. The domain attribute is usually set using the domain name of the sending Web server. Client systems examine the domain attribute when making later http requests. If the server that the client system is accessing falls within the defined DOMAIN_NAME, then the cookie may be sent to the server when making the http request. (The “path” must also be examined as will be explained later.) When a server system falls within the defined DOMAIN_NAME, this is referred to as a “tail match.” Note that a domain name that defines a subset of a domain is deemed to match a larger enclosing domain. For example, the host names “anvil.acme.com” and “shipping.crate.acme.com” fall within the “acme.com” domain.

Only hosts within the specified domain can set a cookie for a domain. The value of the “domain” attribute must have at least two periods in them to prevent accepting values of the form “.com” and “.edu”. If no domain name is specified, then the default value of the “domain” attribute is the domain name of the server that generated the cookie header.

The “path” attribute is used to specify a subset of file system directories in a domain for which the cookie is valid. If a cookie has already passed “domain” matching, then the path name of the URL for a requested document is compared with the “path” attribute. If there is a match, the cookie is considered valid and is sent along with the http request. All the characters of the defined path must match, however there may be additional characters on the path name. Thus, further defined subdirectories will match a path to the parent director. For example, the path “/foo” would match “/foo/bar”, “/foo/bar.html”, and evert “/foobar”, but “/foo” will not match the path “/”. Note that the path “/” is the most general path since it will match any path. If no path is specified when a cookie is created, then the default path will be the same path as the document that was sent with the header which contains the cookie.

The last element of the cookie definition is the optional label of “secure.” If a cookie is marked “secure,” then the cookie will only be retransmitted if there is a secure communication channel to the server system. In a preferred embodiment of the present invention, this means that the cookie will only be sent to HTTPS servers. (HTTP over SSL) If the “secure” attribute is not specified, a cookie is considered safe to be sent over unsecured channels.

The defined extension to the HTTP protocol allows multiple setcookie headers to be issued in a single HTTP response. Each set-cookie header should follow the conventions of the above described format.

Client Behavior

As previously described, when a client receives a set-cookie command in a header, the client system stores the cookie in some type of storage. In order not to place too much burden on client systems, each client system is expected to be able to store only a limited number of cookies. In one embodiment, the storage requirements for the client systems are: <ul id="ul0007" list-style="none"><li id="ul0007-0001" num="0000"><ul id="ul0008" list-style="none"><li id="ul0008-0001" num="0059">(1) 300 total cookies;</li><li id="ul0008-0002" num="0060">(2) 4 kilobytes per cookie; and</li><li id="ul0008-0003" num="0061">(2) 20 cookies per server or domain (note that this rule treats completely specified hosts and domains which are different as separate entities, and each entity has a 20 cookies limitation). <br /> Servers should not expect clients to be able to exceed these limits. When the 300 total cookies or the 20 cookie per server limit is exceeded, clients may delete the least recently used cookie even if the cookie's “expires” time has not passed. </li></ul></li></ul>

If a cookie is received that matches the “NAME”, “domain” and “path” attributes of a previously received cookie, then the previously received cookie will be overwritten. Using this technique, it is possible for a server to delete a cookie previously sent to a client. Specifically, a server that wishes to delete a previous cookie sends a cookie having “expires” time which is in the past that matches the “NAME”, “domain” and “path” attributes of cookie to be deleted. Since the new overwritten cookie contains a expires time that has passed, the cookie will be deleted by the client system. Note “NAME”, “domain” and “path” attributes of the expired cookie must match exactly those of the valid cookie. Since a system must be within the domain that is specified in the domain attribute, it is difficult for any server other than the originator of a cookie to delete or change a cookie.

When a client system that implements the present invention wishes to send an http request to a particular Web server, the client system first examines its cookie list to see if the cookie list contains any matching cookies that need to be sent to the particular Web server. Specifically, before the client sends an http request to a Web server, the client compares the URL of the requested Web document against all of the stored cookies. If any of the cookies in the cookie list matches the requested URL then information containing the name/value pairs of the matching cookies will be sent along with the HTTP request. The format of the line is: <ul id="ul0009" list-style="none"><li id="ul0009-0001" num="0000"><ul id="ul0010" list-style="none"><li id="ul0010-0001" num="0064">Cookie: NAME1=value1; NAME2=value2; . . .</li></ul></li></ul>

When a client sends cookies to a server, all cookies with a more specific path mapping should be sent before cookies with less specific path mappings. For example, a cookie “name1=foo” with a path mapping of “/bar” should be sent before a cookie “name2=foo2” with a path mapping of “/” if they are both to be sent since the path “/bar” is more specific than the global matching path “/”.

Paths having a higher-level value do not override more specific path mappings. If there are multiple matches for a given cookie name, but with separate paths, all the matching cookies will be sent. Thus, both the cookie “name=foo” with a path mapping of “/bar” and the cookie “name=foo” with a path mapping of “/” should be sent since they have different path names.

Some clients access Web servers on the Internet through firewall systems that are designed to prevent unwanted Internet traffic from affecting a local area network coupled to the Internet. Firewall systems often implement “proxy servers” that filter traffic to and from the Internet. It is important that proxy servers not cache Set-cookie commands when caching HTTP information. Thus, if a proxy server receives a response that contains a Set-cookie header, the proxy server should immediately propagate the Set-cookie header to the client. Similarly, if a client system request contains a “Cookie:” header, the cookie header should be forwarded through a proxy even if a conditional “If-modified-since” request is being made.

To further describe the present invention, the following examples describe a set of Web transactions operating in accordance with the present invention:

EXAMPLE 1

A client system requests a Web document from the Web server “telemarking.acme.com” and receives in response: <ul id="ul0011" list-style="none"><li id="ul0011-0001" num="0000"><ul id="ul0012" list-style="none"><li id="ul0012-0001" num="0070">Set-Cookie: CUSTOMER=WILE_E_COYOTE; path=/;</li><li id="ul0012-0002" num="0071">expires=Wednesday, Nov. 9, 1999 23:12:40</li></ul></li></ul>

The client system stores this cookie in a local (client-side) storage unit (e.g. mass storage <b>127</b> or memory <b>125</b>). Since no domain name was specifically identified, the domain will be set to “telemarking.acme.com” since that is the domain name of the server that generated the cookie. When the client later makes an http request for a document in any path (since the path is “/”) of a server system in the telemarking.acme.com domain, the client sends: <ul id="ul0013" list-style="none"><li id="ul0013-0001" num="0000"><ul id="ul0014" list-style="none"><li id="ul0014-0001" num="0073">Cookie: CUSTOMER=WILE_E_COYOTE</li></ul></li></ul>

Assuming the client system makes another request to the telemarking.acme.com domain, the client might receive another cookie from the server such as: <ul id="ul0015" list-style="none"><li id="ul0015-0001" num="0000"><ul id="ul0016" list-style="none"><li id="ul0016-0001" num="0075">Set-Cookie: PART_NUMBER=ROCKET_LAUNCHER;</li><li id="ul0016-0002" num="0076">path=/</li></ul></li></ul>

The client will locally store this additional cookie. Again, no domain name was identified, such that the default domain, “telemarking.acme.com” will be stored. Now, if the client makes yet another request to the “telemarking.acme.com” domain, the client will send all the cookies it has for that domain. Specifically, the client sends: <ul id="ul0017" list-style="none"><li id="ul0017-0001" num="0000"><ul id="ul0018" list-style="none"><li id="ul0018-0001" num="0078">Cookie: CUSTOMER=WILE_E_COYOTE;</li><li id="ul0018-0002" num="0079">PART_NUMBER=ROCKET_LAUNCHER</li></ul></li></ul>

Assuming, the client continues transactions with the “telemarking.acme.com” server, it may receive the following cookie from the server: <ul id="ul0019" list-style="none"><li id="ul0019-0001" num="0000"><ul id="ul0020" list-style="none"><li id="ul0020-0001" num="0081">Set-Cookie: SHIPPING=FEDEX; path=/foo</li></ul></li></ul>

Then, if the client requests a document in path “/” on the “telemarking.acme.com” server, the client will send two cookies as state information: <ul id="ul0021" list-style="none"><li id="ul0021-0001" num="0000"><ul id="ul0022" list-style="none"><li id="ul0022-0001" num="0083">Cookie: CUSTOMER=WILE_E_E_COYOTE;</li><li id="ul0022-0002" num="0084">PART_NUMBER-ROCKET_LAUNCHER</li></ul></li></ul>

Note that the cookie SHIPPING=FEDEX was not sent because the path “/” does not match the path “/foo”. On the other hand, when the client requests a document on the “telemarking.acme.com” server in path “/foo” on this server, then the client will send three cookies as state information; <ul id="ul0023" list-style="none"><li id="ul0023-0001" num="0000"><ul id="ul0024" list-style="none"><li id="ul0024-0001" num="0086">Cookie: CUSTOMER=WILE_E_COYOTE;</li><li id="ul0024-0002" num="0087">PART_NUMBER=ROCKET_LAUNCHER;</li><li id="ul0024-0003" num="0088">SHIPPING=FEDEX</li></ul></li></ul>

EXAMPLE 2

Assume that all of the transactions of Example 1 have been cleared. A client system then requests a Web document from the Web server “telemarking.acme.com” and receives in response: <ul id="ul0025" list-style="none"><li id="ul0025-0001" num="0000"><ul id="ul0026" list-style="none"><li id="ul0026-0001" num="0090">Set Cookie: PART_NUMBER=ROCKET_LAUNCHER_—1;</li><li id="ul0026-0002" num="0091">path=/</li></ul></li></ul>

The client stores this cookie in a local (client-side) storage unit. Since no domain name was specifically identified, the domain will be set to “telemarking.acme.com”. When the client later makes a request to a document in any path of a system in the telemarking.acme.com domain, the client sends back the following data as information: <ul id="ul0027" list-style="none"><li id="ul0027-0001" num="0000"><ul id="ul0028" list-style="none"><li id="ul0028-0001" num="0093">Cookie: PART_NUMBER=ROCKET_LAUNCHER_—1</li></ul></li></ul>

Assuming the client continues to access the “telemarking.acme.com” server, the client may later receive from the server: <ul id="ul0029" list-style="none"><li id="ul0029-0001" num="0000"><ul id="ul0030" list-style="none"><li id="ul0030-0001" num="0095">Set-Cookie: PART_NUMBER=RIDING_ROCKET_—23;</li><li id="ul0030-0002" num="0096">path=/ammo</li></ul></li></ul>

The new cookie has the same name (PART_NUMBER) as an old cookie stored on the client system. Note that the old cookie is not overwritten since the new cookie has a different path attribute: Now, if the client makes a request for a document in the path “/ammo” on the telemarking.acme.com” server, the client should send the following two cookies as state information: <ul id="ul0031" list-style="none"><li id="ul0031-0001" num="0000"><ul id="ul0032" list-style="none"><li id="ul0032-0001" num="0098">Cookie: PART_NUMBER=RIDING_ROCKET_—23;</li><li id="ul0032-0002" num="0099">PART_NUMBER=ROCKET_LAUNCHER_—1</li></ul></li></ul>

Both cookies are sent since the path of the requested document (“/ammo”) matches both the “/” path of the first cookie and the “/ammo” path of the second cookie. Note that the cookie PART_NUMBER=RIDING_ROCKET_—23 is sent first since it has a more specific path (“/ammo”) than the global path (“/”) associated with the cookie PART_NUMBER=ROCKET_LAUNCHER_—1.

An On-line Shopping System Application

To illustrate one possible use of the state information system of the present invention, an implementation of an on-line shopping system will be described. The on-line shopping system allows customers to shop in one or more stores that are implemented as Web servers on the Internet. A customer can browse information on the Web servers that describe products available from the stores. When a desired product is found, the user can place the product into a “virtual shopping basket.” The virtual shopping basket is implemented as a set of cookies that are sent to the client computer system and stored on the client computer system. At check-out time, the customer pays for the selected products using some type of payment system such as a credit card. After payment is received, the on-line shopping system notifies the stores to ship the selected products to the customer. <figref idref="DRAWINGS">FIG. 5</figref> is a flow chart showing the operation of the merchant system during an on-line shopping “trip” by a customer. The customer can run a browser on a client computer system, such as computer system <b>140</b> shown in <figref idref="DRAWINGS">FIG. 6</figref> or client system <b>120</b> shown in <figref idref="DRAWINGS">FIG. 1B</figref> The computer system <b>140</b> of <figref idref="DRAWINGS">FIG. 6</figref> includes a display device <b>142</b> (such as a monitor), a display screen <b>144</b>, a cabinet <b>146</b> (which encloses components typically found in a computer, such as CPU, RAM, ROM, video card, hard drive, sound card, serial ports, etc.), a keyboard <b>148</b>, a mouse <b>150</b>, and a modem <b>152</b>. Mouse <b>150</b> have one or more buttons, such as buttons <b>154</b>. The computer needs to have some type of communication device such as that Modem <b>152</b> allows computer system <b>140</b> to be connected tb the Internet. Other possible communication devices include ethernet network cards.

The customer uses Web browser software to access an on-line “merchant” server that is operated by a merchant having products to sell. This merchant server is a server computer system such as server system <b>122</b> shown in <figref idref="DRAWINGS">FIG. 1B</figref>. Specifically, the browser software sends an http request for the home Web page of a merchant Web server (step <b>212</b>). The merchant Web server responds to the request with an HTML document that is displayed by the browser (step <b>214</b>). The home Web page contains information about the merchant and its products (e.g., shoes, hats, shirts, etc.). The home Web page can implement a set of linked Web pages that describe the products that are available from the merchant. Each product may be associated with its own HTML document that fully describes the product. Products can be described using text, images, sounds, video clips, and any other communication form supported by Web browsers. The user can continue browsing through Web pages of the merchant server by repeating steps <b>212</b>, <b>214</b>, and <b>215</b>.

After browsing through the Web pages provided by the server, the customer may select a product (step <b>216</b>) by, for example, “clicking” (in the conventional manner) on an image of a product that causes the browser to request a Web page that fully describes the product. If the customer wishes to buy shoes from the merchant, the customer could click on a “buy it” button. The merchant server then sends an HTML form document that requests the customer to send necessary details for the purchase (step <b>218</b>). For example, the customer may select a quantity, a desired style, and size of the product as requested by the form document. The browser then sends a POST command under HTTP, which transmits the data entered into the form to the merchant server (step <b>222</b>). The data on the submitted form (e.g., quantity, size, style, etc.) is analyzed by the server and the transaction is processed. The server then generates a synthetic page and sends it to the browser running on the client system. This synthetic page preferably contains a thank you note along with confirmation information. Cookies containing information describing the selected product are also sent at this time (step <b>224</b>).

The browser software running on the client system stores the cookies describing the selected products within the client computer system (step <b>226</b>). The stored cookies include an identification of the contents of a virtual shopping basket that contains the products selected by the consumer. In an embodiment of the present invention, the cookies are stored in a file located in a storage medium (such as a hard disk) of client computer system <b>140</b>.

The time interval for storing the cookies that describe the selected products can be set to any desired length. In one embodiment of the present invention, the cookies are deleted when the customer exits from the browser. This can be accomplished by not setting the “expires” attribute of the product description cookies. In another embodiment of the present invention, the cookies are kept valid (prior to their expiration) even after the customer exits from the browser and turns off computer <b>140</b>. This can be accomplished by setting the “expires” attribute of the product description cookies to a later date.

After selecting a product, the customer may do additional shopping (e.g., buy a hat) from the same store or other stores (step <b>228</b>). In this case, steps <b>212</b>, <b>214</b>, <b>215</b>, <b>216</b>, <b>218</b>, <b>222</b>, <b>224</b> and <b>226</b> need to be performed for the additional products. Each selection of a product in step <b>222</b> will result in the transmission of a cookie from the server to the client, which cookie identifies the selected product. The customer may also exit from the merchant system at any time.

When the customer desires to buy the products, the customer accesses a link that identifies a “check-out” Web page. The check-out Web page causes the browser to send all the product description cookies (<b>230</b>). Thus, the check-out Web page empties out the virtual shopping basket. The merchant server generates a total bill for all the products in the virtual shopping basket. The server may then request billing information (e.g., credit card number) and shipping (e.g., address) information from the customer using a form. In a preferred embodiment the transaction of credit card information is transmitted using a secure medium. The transaction server then performs a real-time credit card authorization. Once the transaction is authorized, transaction server sends messages to individual merchants to fulfill the order (step <b>240</b>).

Other functions could be added to the above described merchant system. For example, several persons could use the same browser for shopping. In this case, the browser identifies the person doing the shopping, and assigns product description cookies to the appropriate person. Thus, each person would have their own virtual shopping basket.

The invention has been described with reference to specific exemplary embodiments thereof and various modifications and changes may be made thereto without departing from the broad spirit and scope of the invention. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense; the invention is limited only by the following claims.