CA2375443C - Secure data exchange between data processing systems - Google Patents
Secure data exchange between data processing systems Download PDFInfo
- Publication number
- CA2375443C CA2375443C CA002375443A CA2375443A CA2375443C CA 2375443 C CA2375443 C CA 2375443C CA 002375443 A CA002375443 A CA 002375443A CA 2375443 A CA2375443 A CA 2375443A CA 2375443 C CA2375443 C CA 2375443C
- Authority
- CA
- Canada
- Prior art keywords
- http
- profile information
- server
- user profile
- http request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/0281—Proxies
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0471—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/561—Adding application-functional data or data for application control, e.g. adding metadata
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Abstract
A data transfer method performed at a proxy server includes intercepting a data request from a client computer that is directed to a target server, encrypting profile information, augmenting the data request by adding the encrypted profile information to the data request, and sending the augmented data request to the target server. A data transfer method that is performed at an information server includes receiving a data request from a proxy server, extracting profile information added to the data request by the proxy server, using the extracted profile information to generate a response, and sending the response to the proxy server.
Description
SECURE DATA EXCHANGE BETWEEN DATA PROCESSING SYSTEMS
BACKGROUND
Fig. 1 shows a computer network 100 that includes both client computers 111-and server computers 131-133. The network 100 also includes data connections that allow the client computers to communicate with the servers. Those data connections include access connections 114-116, a service provider's point of presence (POP) 110, network 120, proxy server 117, and network 130. POP 110 includes data communications equipment that allows a client computer 111-113 to connect to the network 120. For example, POP 110 may include dial-up modem banks, cable modem banks, a T1 interface, wireless communications equipment, or other data transmission equipment.
After a client computer 111-113 has been connected to the network 120 (through POP
110) it may exchange data with other computers on the network 120. Computers on different networks 120 and 130 also can exchange data with each other by sending their data request to proxy server 117 which, in turn, can forward their request to the destination computer, obtain a response from the destination, and return the response to the requesting computer.
The servers 13 1-13 3 and clients 111-113 may communicate with each other using the hypertext transfer protocol (HTTP). HTTP is a data communications protocol that is used by web browser programs (such as Microsoft Internet Explorer and Netscape Navigator) to communicate with web server applications (such as Microsoft Internet Information Server and Netscape Server). Thus, by executing a web browser, a client computer 111-113 can exchange data with a server 131-133 that is executing a web server application.
When a web server receives a HTTP data request from a browser, a web server application, such as a Common Gateway Interface (CGI) script, may be used to query databases, customize responses, and/or perform other processing used to generate a response.
The web server application may need data about the client computer, the browser, its user, and/or other data in order to complete its processing of the data request. For example, a web server application may provide customized weather information based on a user's home address. The web application may obtain the user's address information by sending a data - t -input form to the browser and receiving a user's response that contains the needed information. A web server application also may obtain needed data from web server environmental variables that are populated by data in HTTP
header fields, by a web server, and/or by a web server sub-component. For example, a CGI script's response to a data request may depend on the type of browser originating the request. The CGI script may access a HTTP environment variable ("HTTP_USER_AGENT") populated by the web server using data from a "User-Agent" field in a HTTP header. The value of the HTTP_USER-AGENT variable identifies the type of browser originating a request so that the CGI script can customize its response to that browser.
A web server and a browser also may exchange web cookies that contain data. A web cookie is data file that can be automatically exchanged between browsers and servers along with the request and responses exchanged between the browsers and servers. When a web cookie is received by a browser, it can be stored at the client computer. During future transactions with the web server, the web cookie (and any data that it contains) can be sent back to the web server. By using data stored in web cookies, a web server's need to request data from a user may be reduced. However, since web cookies are typically stored on a client computer, they may be deleted and their data lost. Furthermore, if a user moves to another computer, web cookie information stored on the user's original computer will be unavailable to that user. These factors may reduce the utility of web cookies.
The present inventors recognize that information service systems, such as web servers, should provide convenient, secure, reliable, and simple means of interacting with users. The present inventors further recognize when a server must query a user for data or use web cookies for data storage and input, convenience, security, reliability, and simplicity may suffer.
Consequently, the invention disclosed herein provides additional means of providing information to a web server application that may provide additional flexibility in implementing information systems.
SUMMARY
In general, in one aspect, the invention features a data transfer method performed at a proxy server, the method comprising: intercepting a data request from a client computer that is directed to a target server;
encrypting profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request; and sending the augmented data request to the target server.
In another aspect, the invention features a data transfer method performed at an information server, the method comprising: receiving an augmented data request, wherein the augmented data request includes encrypted user profile information appended to a data request as originally intercepted by a proxy server; extracting the encrypted user profile information added to the data request by the proxy server; using the extracted profile information to generate a response; and sending the response to the proxy server.
In general, in another aspect, the invention features a computer-readable medium with computer-readable code stored thereon, the computer-readable code comprising instructions for causing a computer to: intercept a data request from a client computer that is directed to a target server; encrypt profile information; append the encrypted profile information to the data request as originally intercepted to create an augmented data request; and send the augmented data request to the target server.
In another aspect, the invention features a computer-readable medium with computer-readable code stored thereon, the computer-readable code comprising instructions for causing a computer to: receive a data request comprising encrypted profile information appended to the data request as originally intercepted by a proxy server;
extract the profile information added by the proxy server;
use the extracted profile information to generate a response; and send the response to the proxy server.
In general, in another aspect, the invention features a proxy server comprising: a database comprising records storing user profile information; a network interface operatively coupled to a network to exchange data with a client computer and with a target server; and a processor operatively coupled to the network interface, the database, and a memory comprising executable instructions for causing the processor to intercept a data request that is directed to a target server, retrieve a record from the database, encrypt profile information in the record, append the encrypted profile information to the data request as originally intercepted to create an augmented data request, and send the augmented data request to the target server.
In general, in another aspect, the invention features a proxy server that includes a database, a network interface, a processor, and a memory. The database includes records storing user profile information. The network interface operatively couples the proxy server to a network to exchange data with a client computer and with a target server. The processor is operatively coupled to the network interface, the database, and a memory. The memory includes executable instructions for causing the processor to intercept a data request that is directed to a target server, retrieve a record from the database, encrypt profile information in the record, augment the data request by adding the encrypted profile information, and send the augmented data request to the target server.
In general, in another aspect, the invention features an information server comprising: a network interface operatively coupling the information server to a proxy server; and a processor operatively coupled to the network interface and to a memory comprising executable instructions for causing the processor to receive an augmented data request from the proxy server, wherein the augmented data request includes encrypted user profile information appended to a data request as originally intercepted by the proxy server, decrypt the encrypted user profile information; and use the decrypted user profile information to generate a response to the augmented data request.
In general, in another aspect, the invention features an information server that includes a network interface, a processor, and a memory. The network interface operatively couples the information server to a proxy server. The processor is operatively coupled to the network interface and to the memory. The memory includes executable instructions for causing the processor to receive a data request from the proxy server, decrypt user profile information added to the data request by the target server;
and use the decrypted user profile information to generate a response to the data request.
-4a-In general, in another aspect, the invention features a method performed at a proxy server, the method comprising: intercepting a request from a client;
determining destination information associated with the request; determining that a target server associated with the destination information should receive user profile information; encrypting user profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request;
and sending the augmented request to the target server.
In general, in another aspect, the invention features a system comprising: a proxy server to: intercept a request from a client; determine destination information associated with the request; determine that a target server associated with the destination information should receive user profile information; encrypting user profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request; and send the augmented request to the target server.
According to another aspect of the present invention, there is provided a data transfer method performed by a proxy server, the method comprising:
intercepting an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determining an identity of a user of the client computer in response to receiving the HTTP request; accessing a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers; retrieving an identifier from the accessed storage based on the identity of the user; inserting an additional field into the HTTP
-4b-request to create a modified HTTP request, the additional field containing the retrieved identifier; sending the modified HTTP request to the HTTP server such that the HTTP
server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve the user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receiving the HTTP response from the HTTP server;
and forwarding the HTTP response to the client computer.
According to still another aspect of the present invention, there is provided a data processing method performed by an HTTP server, the method comprising:
receiving a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parsing the modified HTTP request to extract the identifier;
using the extracted identifier to retrieve user profile information from a storage associated with the HTTP server;
generating an HTTP response to the HTTP request based on the retrieved user profile information; and sending the HTTP
response to the proxy server for delivery to a client computer.
According to yet another aspect of the present invention, there is provided a computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing a proxy server to:
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determine an identity of a user of the client computer in response to receiving the -4c-HTTP request; access a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers; retrieve an identifier from the accessed storage based on the identity of the user; insert an additional field into the HTTP
request to create a modified HTTP request, the additional field containing the retrieved identifier; send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP
server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receive the HTTP response from the HTTP server; and forward the HTTP response to the client computer.
According to a further aspect of the present invention, there is provided a computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing an HTTP server to:
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from a storage associated with the HTTP server;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP
response to the proxy server for delivery to a client computer.
-4d-According to yet a further aspect of the present invention, there is provided a proxy server comprising: a storage to store identifiers for use by HTTP servers in retrieving user profile information stored in storages associated with the HTTP servers; a network interface operatively coupled to a network to exchange data with a client computer and with the HTTP server; and a processor operatively coupled to the network interface, the storage, and a memory comprising executable instructions for causing the processor to: intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determine an identity of a user of the client computer in response to receiving the HTTP request; retrieve an identifier from the storage based on the identity of the user; insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier; send the modified HTTP request to the HTTP
server such that the HTTP server parses the modified HTTP
request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receive the HTTP response from the HTTP
server; and forward the HTTP response to the client computer.
According to still a further aspect of the present invention, there is provided an HTTP server comprising: a storage to store user profile information; a network interface operatively coupled to a network to exchange data with a proxy server; and a processor operatively coupled to the network interface and a memory comprising executable -4e-instructions for causing the processor to: receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier; parse the modified HTTP request to extract the identifier; use the extracted identifier to retrieve user profile information from the storage; generate an HTTP response to the HTTP
request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
Implementations may include one or more of the following features. A reference token may be exchanged between servers and used to refer to previously exchanged profile information. The reference token may be placed in subsequent data request sent by the proxy server to the target in place of full profile information. The profile information that is encrypted by the proxy server can be stored in proxy server database records. The particular user profile information encrypted and included in a data request can be selected based on an identity of a client computer user or a browser user. The identity may be determined using the Internet Engineering Task Force IDENT
protocol or by using another method.
Implementations also may include one or more of the following features. Profile information may be encrypted at the proxy server using a session key as an encryption key, and may be decrypted at the target server using the same session key. The session key may be determined by the proxy server and sent to the target server using a public key cryptography algorithm and a public key associated with the target server. A data request may use the hypertext transfer protocol. Profile information -4f-extracted from the data request at the target/information server can be provided to a web application, such as a CGI
script, that is used to generate a response.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Implementations may provide advantages including reduction of redundant data entry, reduction of user data entry errors, secure storage of user data, and automated user profile determination and dissemination.
Different encryption keys can be used for different information servers, and each information server may establish characteristics associated with its encryption key. A web site may dynamically generate, maintain, and change its unique encryption key. This may help to minimize risk of replay attacks, message forgery, and message tampering. In addition, implementations may support multiple levels of security.
Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
-4g-DESCRIPTION OF DRAWINGS
FIG. 1 is a computer network diagram.
FIG. 2 is a computer network diagram.
FIGS. 3A and 3B show exemplary HTTP headers.
FIGS. 4A and 4B are flowcharts.
FIG. 5 is a message flow diagram.
DETAILED DESCRIPTION
Processing of an information request at a information server, such as a web server, can be facilitated by a data transfer mechanism in which data needed to process the request is stored at a proxy server and automatically transferred to the information servers. Such a data transfer mechanism can be used, for example, by an information service provider (ISP) or on-line service provider (OSP) to automatically transfer information about a user (a "user profile") to affiliated web sites. Referring to Fig. 2, to automatically transfer a user profile to a web server 203, the user profile information is first stored at a proxy server 202 in a database 220. When a HTTP data request 211 is received by the proxy server 202 from a web browser 201, the user profile information from database 220 is encapsulated in a request 212 that is forwarded by the proxy server to web server 203. The proxy server 202 encapsulates the user profile information in the request 212 by adding HTTP headers containing the user profile information to the headers received in the request 211.
Figs. 3A and 3B shows fields in HTTP requests. The fields 300 may be fields in a request 211 from a client computer 201, and the fields 350 may be fields in a request 212 forwarded by proxy server 202 to a web site 203. Referring to Figs. 3A and 3B, each field 301-303 includes a HTTP field name and a value associated with the field. HTTP
field names identify the associated field value. For example, the "User-Agent:" field name in field 302 indicates that request 300 originated at a"Mozilla/3.0 compatible" browser;
and the "Cookie:" field name in field 303 includes the value "been_here_before" is a web cookie.
When a HTTP request 211 having fields 300 is received at proxy 202, the proxy server 202 can add user profile information to the request 211 by adding additional HTTP
fields 304-305 containing the profile information, thereby generating a new request 212 with the user profile information encapsulated in fields 304-305.
BACKGROUND
Fig. 1 shows a computer network 100 that includes both client computers 111-and server computers 131-133. The network 100 also includes data connections that allow the client computers to communicate with the servers. Those data connections include access connections 114-116, a service provider's point of presence (POP) 110, network 120, proxy server 117, and network 130. POP 110 includes data communications equipment that allows a client computer 111-113 to connect to the network 120. For example, POP 110 may include dial-up modem banks, cable modem banks, a T1 interface, wireless communications equipment, or other data transmission equipment.
After a client computer 111-113 has been connected to the network 120 (through POP
110) it may exchange data with other computers on the network 120. Computers on different networks 120 and 130 also can exchange data with each other by sending their data request to proxy server 117 which, in turn, can forward their request to the destination computer, obtain a response from the destination, and return the response to the requesting computer.
The servers 13 1-13 3 and clients 111-113 may communicate with each other using the hypertext transfer protocol (HTTP). HTTP is a data communications protocol that is used by web browser programs (such as Microsoft Internet Explorer and Netscape Navigator) to communicate with web server applications (such as Microsoft Internet Information Server and Netscape Server). Thus, by executing a web browser, a client computer 111-113 can exchange data with a server 131-133 that is executing a web server application.
When a web server receives a HTTP data request from a browser, a web server application, such as a Common Gateway Interface (CGI) script, may be used to query databases, customize responses, and/or perform other processing used to generate a response.
The web server application may need data about the client computer, the browser, its user, and/or other data in order to complete its processing of the data request. For example, a web server application may provide customized weather information based on a user's home address. The web application may obtain the user's address information by sending a data - t -input form to the browser and receiving a user's response that contains the needed information. A web server application also may obtain needed data from web server environmental variables that are populated by data in HTTP
header fields, by a web server, and/or by a web server sub-component. For example, a CGI script's response to a data request may depend on the type of browser originating the request. The CGI script may access a HTTP environment variable ("HTTP_USER_AGENT") populated by the web server using data from a "User-Agent" field in a HTTP header. The value of the HTTP_USER-AGENT variable identifies the type of browser originating a request so that the CGI script can customize its response to that browser.
A web server and a browser also may exchange web cookies that contain data. A web cookie is data file that can be automatically exchanged between browsers and servers along with the request and responses exchanged between the browsers and servers. When a web cookie is received by a browser, it can be stored at the client computer. During future transactions with the web server, the web cookie (and any data that it contains) can be sent back to the web server. By using data stored in web cookies, a web server's need to request data from a user may be reduced. However, since web cookies are typically stored on a client computer, they may be deleted and their data lost. Furthermore, if a user moves to another computer, web cookie information stored on the user's original computer will be unavailable to that user. These factors may reduce the utility of web cookies.
The present inventors recognize that information service systems, such as web servers, should provide convenient, secure, reliable, and simple means of interacting with users. The present inventors further recognize when a server must query a user for data or use web cookies for data storage and input, convenience, security, reliability, and simplicity may suffer.
Consequently, the invention disclosed herein provides additional means of providing information to a web server application that may provide additional flexibility in implementing information systems.
SUMMARY
In general, in one aspect, the invention features a data transfer method performed at a proxy server, the method comprising: intercepting a data request from a client computer that is directed to a target server;
encrypting profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request; and sending the augmented data request to the target server.
In another aspect, the invention features a data transfer method performed at an information server, the method comprising: receiving an augmented data request, wherein the augmented data request includes encrypted user profile information appended to a data request as originally intercepted by a proxy server; extracting the encrypted user profile information added to the data request by the proxy server; using the extracted profile information to generate a response; and sending the response to the proxy server.
In general, in another aspect, the invention features a computer-readable medium with computer-readable code stored thereon, the computer-readable code comprising instructions for causing a computer to: intercept a data request from a client computer that is directed to a target server; encrypt profile information; append the encrypted profile information to the data request as originally intercepted to create an augmented data request; and send the augmented data request to the target server.
In another aspect, the invention features a computer-readable medium with computer-readable code stored thereon, the computer-readable code comprising instructions for causing a computer to: receive a data request comprising encrypted profile information appended to the data request as originally intercepted by a proxy server;
extract the profile information added by the proxy server;
use the extracted profile information to generate a response; and send the response to the proxy server.
In general, in another aspect, the invention features a proxy server comprising: a database comprising records storing user profile information; a network interface operatively coupled to a network to exchange data with a client computer and with a target server; and a processor operatively coupled to the network interface, the database, and a memory comprising executable instructions for causing the processor to intercept a data request that is directed to a target server, retrieve a record from the database, encrypt profile information in the record, append the encrypted profile information to the data request as originally intercepted to create an augmented data request, and send the augmented data request to the target server.
In general, in another aspect, the invention features a proxy server that includes a database, a network interface, a processor, and a memory. The database includes records storing user profile information. The network interface operatively couples the proxy server to a network to exchange data with a client computer and with a target server. The processor is operatively coupled to the network interface, the database, and a memory. The memory includes executable instructions for causing the processor to intercept a data request that is directed to a target server, retrieve a record from the database, encrypt profile information in the record, augment the data request by adding the encrypted profile information, and send the augmented data request to the target server.
In general, in another aspect, the invention features an information server comprising: a network interface operatively coupling the information server to a proxy server; and a processor operatively coupled to the network interface and to a memory comprising executable instructions for causing the processor to receive an augmented data request from the proxy server, wherein the augmented data request includes encrypted user profile information appended to a data request as originally intercepted by the proxy server, decrypt the encrypted user profile information; and use the decrypted user profile information to generate a response to the augmented data request.
In general, in another aspect, the invention features an information server that includes a network interface, a processor, and a memory. The network interface operatively couples the information server to a proxy server. The processor is operatively coupled to the network interface and to the memory. The memory includes executable instructions for causing the processor to receive a data request from the proxy server, decrypt user profile information added to the data request by the target server;
and use the decrypted user profile information to generate a response to the data request.
-4a-In general, in another aspect, the invention features a method performed at a proxy server, the method comprising: intercepting a request from a client;
determining destination information associated with the request; determining that a target server associated with the destination information should receive user profile information; encrypting user profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request;
and sending the augmented request to the target server.
In general, in another aspect, the invention features a system comprising: a proxy server to: intercept a request from a client; determine destination information associated with the request; determine that a target server associated with the destination information should receive user profile information; encrypting user profile information; appending the encrypted profile information to the data request as originally intercepted to create an augmented data request; and send the augmented request to the target server.
According to another aspect of the present invention, there is provided a data transfer method performed by a proxy server, the method comprising:
intercepting an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determining an identity of a user of the client computer in response to receiving the HTTP request; accessing a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers; retrieving an identifier from the accessed storage based on the identity of the user; inserting an additional field into the HTTP
-4b-request to create a modified HTTP request, the additional field containing the retrieved identifier; sending the modified HTTP request to the HTTP server such that the HTTP
server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve the user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receiving the HTTP response from the HTTP server;
and forwarding the HTTP response to the client computer.
According to still another aspect of the present invention, there is provided a data processing method performed by an HTTP server, the method comprising:
receiving a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parsing the modified HTTP request to extract the identifier;
using the extracted identifier to retrieve user profile information from a storage associated with the HTTP server;
generating an HTTP response to the HTTP request based on the retrieved user profile information; and sending the HTTP
response to the proxy server for delivery to a client computer.
According to yet another aspect of the present invention, there is provided a computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing a proxy server to:
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determine an identity of a user of the client computer in response to receiving the -4c-HTTP request; access a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers; retrieve an identifier from the accessed storage based on the identity of the user; insert an additional field into the HTTP
request to create a modified HTTP request, the additional field containing the retrieved identifier; send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP
server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receive the HTTP response from the HTTP server; and forward the HTTP response to the client computer.
According to a further aspect of the present invention, there is provided a computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing an HTTP server to:
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from a storage associated with the HTTP server;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP
response to the proxy server for delivery to a client computer.
-4d-According to yet a further aspect of the present invention, there is provided a proxy server comprising: a storage to store identifiers for use by HTTP servers in retrieving user profile information stored in storages associated with the HTTP servers; a network interface operatively coupled to a network to exchange data with a client computer and with the HTTP server; and a processor operatively coupled to the network interface, the storage, and a memory comprising executable instructions for causing the processor to: intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields; determine an identity of a user of the client computer in response to receiving the HTTP request; retrieve an identifier from the storage based on the identity of the user; insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier; send the modified HTTP request to the HTTP
server such that the HTTP server parses the modified HTTP
request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server; receive the HTTP response from the HTTP
server; and forward the HTTP response to the client computer.
According to still a further aspect of the present invention, there is provided an HTTP server comprising: a storage to store user profile information; a network interface operatively coupled to a network to exchange data with a proxy server; and a processor operatively coupled to the network interface and a memory comprising executable -4e-instructions for causing the processor to: receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier; parse the modified HTTP request to extract the identifier; use the extracted identifier to retrieve user profile information from the storage; generate an HTTP response to the HTTP
request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
Implementations may include one or more of the following features. A reference token may be exchanged between servers and used to refer to previously exchanged profile information. The reference token may be placed in subsequent data request sent by the proxy server to the target in place of full profile information. The profile information that is encrypted by the proxy server can be stored in proxy server database records. The particular user profile information encrypted and included in a data request can be selected based on an identity of a client computer user or a browser user. The identity may be determined using the Internet Engineering Task Force IDENT
protocol or by using another method.
Implementations also may include one or more of the following features. Profile information may be encrypted at the proxy server using a session key as an encryption key, and may be decrypted at the target server using the same session key. The session key may be determined by the proxy server and sent to the target server using a public key cryptography algorithm and a public key associated with the target server. A data request may use the hypertext transfer protocol. Profile information -4f-extracted from the data request at the target/information server can be provided to a web application, such as a CGI
script, that is used to generate a response.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Implementations may provide advantages including reduction of redundant data entry, reduction of user data entry errors, secure storage of user data, and automated user profile determination and dissemination.
Different encryption keys can be used for different information servers, and each information server may establish characteristics associated with its encryption key. A web site may dynamically generate, maintain, and change its unique encryption key. This may help to minimize risk of replay attacks, message forgery, and message tampering. In addition, implementations may support multiple levels of security.
Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
-4g-DESCRIPTION OF DRAWINGS
FIG. 1 is a computer network diagram.
FIG. 2 is a computer network diagram.
FIGS. 3A and 3B show exemplary HTTP headers.
FIGS. 4A and 4B are flowcharts.
FIG. 5 is a message flow diagram.
DETAILED DESCRIPTION
Processing of an information request at a information server, such as a web server, can be facilitated by a data transfer mechanism in which data needed to process the request is stored at a proxy server and automatically transferred to the information servers. Such a data transfer mechanism can be used, for example, by an information service provider (ISP) or on-line service provider (OSP) to automatically transfer information about a user (a "user profile") to affiliated web sites. Referring to Fig. 2, to automatically transfer a user profile to a web server 203, the user profile information is first stored at a proxy server 202 in a database 220. When a HTTP data request 211 is received by the proxy server 202 from a web browser 201, the user profile information from database 220 is encapsulated in a request 212 that is forwarded by the proxy server to web server 203. The proxy server 202 encapsulates the user profile information in the request 212 by adding HTTP headers containing the user profile information to the headers received in the request 211.
Figs. 3A and 3B shows fields in HTTP requests. The fields 300 may be fields in a request 211 from a client computer 201, and the fields 350 may be fields in a request 212 forwarded by proxy server 202 to a web site 203. Referring to Figs. 3A and 3B, each field 301-303 includes a HTTP field name and a value associated with the field. HTTP
field names identify the associated field value. For example, the "User-Agent:" field name in field 302 indicates that request 300 originated at a"Mozilla/3.0 compatible" browser;
and the "Cookie:" field name in field 303 includes the value "been_here_before" is a web cookie.
When a HTTP request 211 having fields 300 is received at proxy 202, the proxy server 202 can add user profile information to the request 211 by adding additional HTTP
fields 304-305 containing the profile information, thereby generating a new request 212 with the user profile information encapsulated in fields 304-305.
Database 220 may be a local or remote database that can store multiple user profiles.
For example, the database 220 may be a database storing user profiles on a hard disk directly connected to the proxy server 202, or the database may be a SQL database at a remote system and accessed over a TCP/IP connection. Still other database 220 implementations may be used. Each user profile may be associated with a particular user or group of users. A user profile may be selected from the database 220 based on the identifying information associated with a particular computer or user of that computer. To determine the user's identity, a proxy server may use a table or database that associates user identity information with network connection information. For example, referring to Figs. 2, 4A, and 4B, when a io client computer 201 connects to a network 230, the client computer's user may submit name and password information to a POP or to a login server. The POP or login server may then send the user name and network connection information unique to that user (such as a unique combination of TCP/IP address and port number) to the proxy server 202 where it is stored in a database 220 (step 400). When the proxy server 202 receives a subsequent HTTP request 211 (step 401), the proxy server can identify the user associated with the request by querying the database of stored name and network connection associations. A proxy server also may identify a user using the IDENT protocol. The IDENT protocol is an Internet protocol that allows a computer to ask another computer for the name of the user. The IDENT
protocol is further described in Internet Engineering Task Force (IETF) document RFC 1413.
When the proxy server 202 has identified the user (step 402), the proxy server can retrieve a user profile associated with that user from its database 220. The proxy server may then add HTTP fields containing user profile information to fields in the original HTTP
request 211 (step 403). For example, header fields 304-305 may be added to the original header fields 301-303 from request 211. Field 304 may include unencrypted user profile data ("UserName=John_Doe, ZipCode=60609, ParentalControl=YoungTeen), while field may include encrypted user profile data. Encryption of data in the field 305 may use the SecureData protocol (explained later). The proxy server thereby forms the modified HTTP
request 212 containing the user profile data. The modified request 212 may then be forwarded by the proxy server for receipt at a web site (steps 404 and 421).
Particular web servers may or may not be configured to recognize the user profile data fields 304-305. A web server that is not configured to recognize the user profile fields 304-305 may ignore the fields. A web server that is configured to recognize the user profile fields 304-305 can extract the profile data from the field 304-305 (steps 422 and 424).
Extraction of user profile data in the field 305 may include decryption of the user profile data in encrypted field 305. The extracted user profile data can be used, for example, to generate or customize data sent in response 213 to the proxy server for forwarding as a response 214 to a user or client computer (step 425). For example, a tourist information web server may customize a page based user profile data specifying a browser user's age, and interest. If a io web server looks for a user profile field 304-305 in the request 212, and the user profile field is not present, the server may use "traditional" data input mechanisms (such as forms and web cookies) to obtain needed data from a user (step 422-423). After the necessary data is obtained, the web server 203 can generate a response (step 425).
Exchange of user profile data between a proxy server 202 and a web server 203 may implemented using custom filtering software ("proxy data exchange filter"
software) that can be added to commercially available proxy and web site server software. For example, Microsoft Internet Information Server (IIS) provides an application programming interface known as the information server application programming interface (ISAPI) that allows custom filtering software to be added to an IIS web site. A Netscape web site server provides an application programming interface known as the Netscape server application programming interface (NSAPI) that may also be used to develcrk:, custom filtering software.
When a request 212 from the proxy server 203 is received at an IIS or Netscape server web site, the request 212 is passed to the proxy data exchange filter by the IIS
or Netscape server software and the user profile data is extracted from the headers 304-305. The extracted profile data may then be made available as HTTP environment variables, database entries, or other data exchange structures that can be used by web applications. The remaining header information in request 212 (e.g., the original information from request 211), may then be processed by the web server to obtain response 213 information.
A proxy server 202 and web server 203 may implement the SecureData protocol (described below) to encrypt user profile data. Encrypted user profile data may be indicated by a special HTTP header. For example, the field name "User-Profile-SecureData" in field 305 indicates that the field value segment of field 305 contains encrypted profile data.
The SecureData protocol uses multiple cryptography algorithms to provide secure user profile data transfers between a proxy server 202 and a web server 203.
For example, the SecureData protocol may use the Rivest, Shamir, Adelman (RSA) public key encryption algorithm or the pretty-good-privacy (PGP) public key cryptography algorithm along with the RSA RC4 symmetric encryption algorithm. Additional information on the RC4 algorithm can be found, for example, in Applied Cryptography, 2nd edition, By Bruce Schneier, John Wiley & Sons, 1996.
User profile information may be encrypted at proxy server 202 using a symmetric encryption algorithm. A symmetric encryption algorithm, such as the RSA RC4 algorithm, uses the same encryption key (referred to herein as a "session" key) to encrypt and decrypt data. The proxy server 202 may encrypt user profile data and place it in a HTTP field in request message 212. The proxy server 202 can also separately encrypt the session key using a public key cryptography algorithm and the public key of the web server 203.
The public key encrypted session key may also be placed in the request message 212, or may be sent separately to the web server 203. When the web server 203 has received the encrypted session key and user profile data, the web server 203 can decrypt its session key by using the public key cryptography algorithm and the web server's private key. The web server 203 may then decrypt the user profile information using the decrypted session key.
Fig. 5 shows further details of an implementation in which a request message may include both the encrypted session key and the encrypted user profile data.
Referring to Fig. 5, when a request 511 is received at the proxy server 502, the proxy server determines whether it should add encrypted user profile data to the request. To do so, the proxy server may extract a destination web site address from URL
information in the request 511, and query a database to determine whether the destination web site is to receive user profile information and whether the information is to be encrypted. If the destination web site is to receive encrypted user profile information, the proxy server 502 may then query its database to determine whether it has a valid public key for the web server 503. If the proxy server 502 has a valid public key, the proxy server can use the public key to encrypt session key information that can be provided to a symmetric encryption algorithm to encrypt user profile data. The encrypted session key and user profile data may then be forwarded in requests 514 to the web server 503.
If the proxy server 502 does not have a valid public key for web server 503, the proxy server will obtain the public key from the web server 503 using a HTTP request 512. The request 512 includes a URL that identifies a public key file ("pub_key_file") stored on the server 503. The public key file may include additional information used by the proxy server 502. For example, the public key file may include the length of the public key, a SecureData protocol version number, a list of supported encryption algorithms, and shortcut configuration information ("shortcut" information is further explained, below).
~
An exemplary public key may have the format shown below (chevrons `<' and'>' delineate fields in the public key file and brackets `[` and `]' delineate optional information):
Exemplary Public Key File <public key = length-of-key key>
[<Version = SecureData protocol version number>]
[<crypto = <encryption method>]
[<shortcut =[nonejlowjmedjhigh1max]>]
The web server's public key file is returned to the proxy server 503 in a HTTP
response 513. The web server 503 may provide additional SecureData protocol information in HTTP fields of response 513 and/or in the public key file returned by the response message 513. For example, HTTP fields in response 513 may specify a time to live (TTL) for the key. The TTL value can be used to indicate the period during which the public key is valid.
A proxy server 502 or web server 503 may check a SecureData protocol version number returned in the public key file, in request 512 and/or in response 513 to ensure that the protocol is functioning properly and to recover from or to avoid errors.
For example, if a proxy server 502 detects that protocol versions numbers in a retrieved public key file and those in a header of a response 513 do not match, the proxy server may re-submit the request 512 to the server 503. When the request 512 is re-submitted, the proxy server 502 can include the HTTP "no-cache" pragma to instruct caching systems between the proxy 502 and the web server 503 not to use cached data. This may help avoid errors introduced by using stale cached data. When the proxy server 502 has received the web server's public key, it may cache the public key subject to a time-to-live (TTL) value specified by the web server 503 and/or the proxy server's own TTL policies.
If the proxy server 502 is unable to retrieve a web server's public key information or the public key information is otherwise unusable, the proxy server can add a problem report information to fields in a HTTP request 514 to indicate why the public key information is unusable. For example, the proxy server may indicate that the key information has been corrupted or a protocol version number or encryption level specified in the public key file is not supported. If the a web server's public key information is unusable and, consequently, the SecureData encryption protocol cannot be used, a proxy server may continue to forward the .
HTTP requests from browser clients to the web server without adding additional SecureData proxy headers. Alternatively the proxy server may block or otherwise filter request to the web server. The specific behavior may be defined on a per-web server basis using configuration information stored at the proxy server 502.
Once the proxy server 502 has the public key of web server 503, the proxy server can use the public key to encrypt session key data. The encrypted session key data may then be added to HTTP fields in the request from a browser or client computer 511 to form a modified request 514 that includes the public-key-encrypted session key information. The proxy server also can encrypt the user profile data using the session key information and a symmetric encryption algorithm and place the encrypted user profile data in HTTP fields in the modified request 514. For example, referring to Fig. 3B, the field 305 includes session key data "session=a3f792b210dafad" that may be public-key encrypted, and user profile data "Profile =A389C2ZA845MRAS02VMA39v1Z93AYC39AC3ABCEG78BB" that may be encrypted using a symmetric algorithm.
Different web server's or groups of web servers can have different session keys. A
web server's session key may be formed by combining a "master" session key that is the same for a group of web servers with a key mask that can be used to create a unique session key for a web server or a group of web servers. For example, a 64-bit master session key may be combined with a 64-bit key mask using an exclusive-or ('XOR') operation, to yield a unique 64-bit session key. In some implementations, the master session key may be the proxy server's public key. Other methods of generating unique keys can be used. The session key data can in field 305 (e.g., "session=a3f792b210dafad") can include numerous sub-fields. For example, the session key data can include a master key, a key mask, a timestamp, a URL
hash, a Proxy IP field, and an encoding scheme field. These fields can contain the following data:
Master key: The master key is a value that is generated by the SecureData proxy server that can be combined with a key mask to generate a unique session key. The proxy server may periodically generate a new master session key. For example, a new master session key may be generated every n minutes. The Master key may be the proxy io server's public key.
Key mask: The key mask is a value generated by a SecureData proxy server that is unique to a particular web site and which can be combined with a master key to generate a unique session key for that web site. A master key and a key mask can be combined using an exclusive-or ('XOR') operation, by appending the keys together, or by another key combination algorithm. A new key mask may be periodically generated.
For example, a new key mask may be generated every n minutes.
Timestamp: A timestamp value may be added to the public-key encrypted data to make replay attacks more difficult. The timestamp value can be checked by the receiving web server and compared to the current time. If the difference between the timestamp value and current time exceeds a threshold value, the re(: may be denied or other error recovery or security procedures may be employed.
URL hash: A hash value derived from a requested URL may be added to the public-key encrypted data to make forging or tampering more difficult.
Proxy IP: The IP address of the proxy server be inserted in the session key data. When a request 514 is received at a web server 503, the web server may compare the IP
address in the proxy IP field to help confirm that the request came from a particular proxy server 502. If the addresses differ, the request 514 may be rejected or other error recovery or security procedures may be employed.
Encoding scheme: Encoding scheme data may be sent from the SecureData proxy server to a SecureData web server to identify how user profile data is encoded. For example, the encoding scheme value may indicate that profile data is in a binary (bin) form, or in name-value pair (nvp) form (which may be expressed using the Abstract Syntax Notation 1 (ASN. 1) or other name-value coding scheme), or in another form.
The proxy server 502 can use a web server's unique session key to encrypt user profile data that is add it to the field 305. In some implementations, the user profile data may be placed in one or more additional fields. The request 514, now containing the public-key encrypted session data and the symmetric encrypted user profile data, is then sent to web server 503.
When request 514 is received by the web server 503, the request can be passed to proxy data exchange filter software that can extract the added field's 304-205 from the request 514, decrypt the session key and the user profile information contained in the fields 304-205, and make the user profile information available to web server applications.
The user profile information may be made available to web server applications by setting HTTP
environment variables, by storing it in a database, by placing it in shared memory, and/or using other data exchange techniques. The proxy data exchange filter software may then pass the request 514 back to the web server for further processing and for generation of a response 515.
The web server 503 can store received profile data in a local database for future request processing purposes. The web server 503 may return a shortcut token to the proxy server 502. The proxy server 502 may add the shortcut token to a subsequent request 518 in place of the `full' user profile data sent in the request 514. This can be used to reduce the amount of data that needs be transferred in subsequent request 518. A shortcut token can be an index value, database query information, file name, other pointer data, or an arbitrary value generated by the web site 503 and used to reference the stored user profile data.
A web server's public key file may be sent to the proxy server 502 using a security level specified by the site 503. For example, a web site's public key file include data indicating that the web site will use a specified one of the following shortcut key security levels:
none: If "none" is specified, the shortcut token is sent to the proxy server as a clear (e.g., unencrypted value).
For example, the database 220 may be a database storing user profiles on a hard disk directly connected to the proxy server 202, or the database may be a SQL database at a remote system and accessed over a TCP/IP connection. Still other database 220 implementations may be used. Each user profile may be associated with a particular user or group of users. A user profile may be selected from the database 220 based on the identifying information associated with a particular computer or user of that computer. To determine the user's identity, a proxy server may use a table or database that associates user identity information with network connection information. For example, referring to Figs. 2, 4A, and 4B, when a io client computer 201 connects to a network 230, the client computer's user may submit name and password information to a POP or to a login server. The POP or login server may then send the user name and network connection information unique to that user (such as a unique combination of TCP/IP address and port number) to the proxy server 202 where it is stored in a database 220 (step 400). When the proxy server 202 receives a subsequent HTTP request 211 (step 401), the proxy server can identify the user associated with the request by querying the database of stored name and network connection associations. A proxy server also may identify a user using the IDENT protocol. The IDENT protocol is an Internet protocol that allows a computer to ask another computer for the name of the user. The IDENT
protocol is further described in Internet Engineering Task Force (IETF) document RFC 1413.
When the proxy server 202 has identified the user (step 402), the proxy server can retrieve a user profile associated with that user from its database 220. The proxy server may then add HTTP fields containing user profile information to fields in the original HTTP
request 211 (step 403). For example, header fields 304-305 may be added to the original header fields 301-303 from request 211. Field 304 may include unencrypted user profile data ("UserName=John_Doe, ZipCode=60609, ParentalControl=YoungTeen), while field may include encrypted user profile data. Encryption of data in the field 305 may use the SecureData protocol (explained later). The proxy server thereby forms the modified HTTP
request 212 containing the user profile data. The modified request 212 may then be forwarded by the proxy server for receipt at a web site (steps 404 and 421).
Particular web servers may or may not be configured to recognize the user profile data fields 304-305. A web server that is not configured to recognize the user profile fields 304-305 may ignore the fields. A web server that is configured to recognize the user profile fields 304-305 can extract the profile data from the field 304-305 (steps 422 and 424).
Extraction of user profile data in the field 305 may include decryption of the user profile data in encrypted field 305. The extracted user profile data can be used, for example, to generate or customize data sent in response 213 to the proxy server for forwarding as a response 214 to a user or client computer (step 425). For example, a tourist information web server may customize a page based user profile data specifying a browser user's age, and interest. If a io web server looks for a user profile field 304-305 in the request 212, and the user profile field is not present, the server may use "traditional" data input mechanisms (such as forms and web cookies) to obtain needed data from a user (step 422-423). After the necessary data is obtained, the web server 203 can generate a response (step 425).
Exchange of user profile data between a proxy server 202 and a web server 203 may implemented using custom filtering software ("proxy data exchange filter"
software) that can be added to commercially available proxy and web site server software. For example, Microsoft Internet Information Server (IIS) provides an application programming interface known as the information server application programming interface (ISAPI) that allows custom filtering software to be added to an IIS web site. A Netscape web site server provides an application programming interface known as the Netscape server application programming interface (NSAPI) that may also be used to develcrk:, custom filtering software.
When a request 212 from the proxy server 203 is received at an IIS or Netscape server web site, the request 212 is passed to the proxy data exchange filter by the IIS
or Netscape server software and the user profile data is extracted from the headers 304-305. The extracted profile data may then be made available as HTTP environment variables, database entries, or other data exchange structures that can be used by web applications. The remaining header information in request 212 (e.g., the original information from request 211), may then be processed by the web server to obtain response 213 information.
A proxy server 202 and web server 203 may implement the SecureData protocol (described below) to encrypt user profile data. Encrypted user profile data may be indicated by a special HTTP header. For example, the field name "User-Profile-SecureData" in field 305 indicates that the field value segment of field 305 contains encrypted profile data.
The SecureData protocol uses multiple cryptography algorithms to provide secure user profile data transfers between a proxy server 202 and a web server 203.
For example, the SecureData protocol may use the Rivest, Shamir, Adelman (RSA) public key encryption algorithm or the pretty-good-privacy (PGP) public key cryptography algorithm along with the RSA RC4 symmetric encryption algorithm. Additional information on the RC4 algorithm can be found, for example, in Applied Cryptography, 2nd edition, By Bruce Schneier, John Wiley & Sons, 1996.
User profile information may be encrypted at proxy server 202 using a symmetric encryption algorithm. A symmetric encryption algorithm, such as the RSA RC4 algorithm, uses the same encryption key (referred to herein as a "session" key) to encrypt and decrypt data. The proxy server 202 may encrypt user profile data and place it in a HTTP field in request message 212. The proxy server 202 can also separately encrypt the session key using a public key cryptography algorithm and the public key of the web server 203.
The public key encrypted session key may also be placed in the request message 212, or may be sent separately to the web server 203. When the web server 203 has received the encrypted session key and user profile data, the web server 203 can decrypt its session key by using the public key cryptography algorithm and the web server's private key. The web server 203 may then decrypt the user profile information using the decrypted session key.
Fig. 5 shows further details of an implementation in which a request message may include both the encrypted session key and the encrypted user profile data.
Referring to Fig. 5, when a request 511 is received at the proxy server 502, the proxy server determines whether it should add encrypted user profile data to the request. To do so, the proxy server may extract a destination web site address from URL
information in the request 511, and query a database to determine whether the destination web site is to receive user profile information and whether the information is to be encrypted. If the destination web site is to receive encrypted user profile information, the proxy server 502 may then query its database to determine whether it has a valid public key for the web server 503. If the proxy server 502 has a valid public key, the proxy server can use the public key to encrypt session key information that can be provided to a symmetric encryption algorithm to encrypt user profile data. The encrypted session key and user profile data may then be forwarded in requests 514 to the web server 503.
If the proxy server 502 does not have a valid public key for web server 503, the proxy server will obtain the public key from the web server 503 using a HTTP request 512. The request 512 includes a URL that identifies a public key file ("pub_key_file") stored on the server 503. The public key file may include additional information used by the proxy server 502. For example, the public key file may include the length of the public key, a SecureData protocol version number, a list of supported encryption algorithms, and shortcut configuration information ("shortcut" information is further explained, below).
~
An exemplary public key may have the format shown below (chevrons `<' and'>' delineate fields in the public key file and brackets `[` and `]' delineate optional information):
Exemplary Public Key File <public key = length-of-key key>
[<Version = SecureData protocol version number>]
[<crypto = <encryption method>]
[<shortcut =[nonejlowjmedjhigh1max]>]
The web server's public key file is returned to the proxy server 503 in a HTTP
response 513. The web server 503 may provide additional SecureData protocol information in HTTP fields of response 513 and/or in the public key file returned by the response message 513. For example, HTTP fields in response 513 may specify a time to live (TTL) for the key. The TTL value can be used to indicate the period during which the public key is valid.
A proxy server 502 or web server 503 may check a SecureData protocol version number returned in the public key file, in request 512 and/or in response 513 to ensure that the protocol is functioning properly and to recover from or to avoid errors.
For example, if a proxy server 502 detects that protocol versions numbers in a retrieved public key file and those in a header of a response 513 do not match, the proxy server may re-submit the request 512 to the server 503. When the request 512 is re-submitted, the proxy server 502 can include the HTTP "no-cache" pragma to instruct caching systems between the proxy 502 and the web server 503 not to use cached data. This may help avoid errors introduced by using stale cached data. When the proxy server 502 has received the web server's public key, it may cache the public key subject to a time-to-live (TTL) value specified by the web server 503 and/or the proxy server's own TTL policies.
If the proxy server 502 is unable to retrieve a web server's public key information or the public key information is otherwise unusable, the proxy server can add a problem report information to fields in a HTTP request 514 to indicate why the public key information is unusable. For example, the proxy server may indicate that the key information has been corrupted or a protocol version number or encryption level specified in the public key file is not supported. If the a web server's public key information is unusable and, consequently, the SecureData encryption protocol cannot be used, a proxy server may continue to forward the .
HTTP requests from browser clients to the web server without adding additional SecureData proxy headers. Alternatively the proxy server may block or otherwise filter request to the web server. The specific behavior may be defined on a per-web server basis using configuration information stored at the proxy server 502.
Once the proxy server 502 has the public key of web server 503, the proxy server can use the public key to encrypt session key data. The encrypted session key data may then be added to HTTP fields in the request from a browser or client computer 511 to form a modified request 514 that includes the public-key-encrypted session key information. The proxy server also can encrypt the user profile data using the session key information and a symmetric encryption algorithm and place the encrypted user profile data in HTTP fields in the modified request 514. For example, referring to Fig. 3B, the field 305 includes session key data "session=a3f792b210dafad" that may be public-key encrypted, and user profile data "Profile =A389C2ZA845MRAS02VMA39v1Z93AYC39AC3ABCEG78BB" that may be encrypted using a symmetric algorithm.
Different web server's or groups of web servers can have different session keys. A
web server's session key may be formed by combining a "master" session key that is the same for a group of web servers with a key mask that can be used to create a unique session key for a web server or a group of web servers. For example, a 64-bit master session key may be combined with a 64-bit key mask using an exclusive-or ('XOR') operation, to yield a unique 64-bit session key. In some implementations, the master session key may be the proxy server's public key. Other methods of generating unique keys can be used. The session key data can in field 305 (e.g., "session=a3f792b210dafad") can include numerous sub-fields. For example, the session key data can include a master key, a key mask, a timestamp, a URL
hash, a Proxy IP field, and an encoding scheme field. These fields can contain the following data:
Master key: The master key is a value that is generated by the SecureData proxy server that can be combined with a key mask to generate a unique session key. The proxy server may periodically generate a new master session key. For example, a new master session key may be generated every n minutes. The Master key may be the proxy io server's public key.
Key mask: The key mask is a value generated by a SecureData proxy server that is unique to a particular web site and which can be combined with a master key to generate a unique session key for that web site. A master key and a key mask can be combined using an exclusive-or ('XOR') operation, by appending the keys together, or by another key combination algorithm. A new key mask may be periodically generated.
For example, a new key mask may be generated every n minutes.
Timestamp: A timestamp value may be added to the public-key encrypted data to make replay attacks more difficult. The timestamp value can be checked by the receiving web server and compared to the current time. If the difference between the timestamp value and current time exceeds a threshold value, the re(: may be denied or other error recovery or security procedures may be employed.
URL hash: A hash value derived from a requested URL may be added to the public-key encrypted data to make forging or tampering more difficult.
Proxy IP: The IP address of the proxy server be inserted in the session key data. When a request 514 is received at a web server 503, the web server may compare the IP
address in the proxy IP field to help confirm that the request came from a particular proxy server 502. If the addresses differ, the request 514 may be rejected or other error recovery or security procedures may be employed.
Encoding scheme: Encoding scheme data may be sent from the SecureData proxy server to a SecureData web server to identify how user profile data is encoded. For example, the encoding scheme value may indicate that profile data is in a binary (bin) form, or in name-value pair (nvp) form (which may be expressed using the Abstract Syntax Notation 1 (ASN. 1) or other name-value coding scheme), or in another form.
The proxy server 502 can use a web server's unique session key to encrypt user profile data that is add it to the field 305. In some implementations, the user profile data may be placed in one or more additional fields. The request 514, now containing the public-key encrypted session data and the symmetric encrypted user profile data, is then sent to web server 503.
When request 514 is received by the web server 503, the request can be passed to proxy data exchange filter software that can extract the added field's 304-205 from the request 514, decrypt the session key and the user profile information contained in the fields 304-205, and make the user profile information available to web server applications.
The user profile information may be made available to web server applications by setting HTTP
environment variables, by storing it in a database, by placing it in shared memory, and/or using other data exchange techniques. The proxy data exchange filter software may then pass the request 514 back to the web server for further processing and for generation of a response 515.
The web server 503 can store received profile data in a local database for future request processing purposes. The web server 503 may return a shortcut token to the proxy server 502. The proxy server 502 may add the shortcut token to a subsequent request 518 in place of the `full' user profile data sent in the request 514. This can be used to reduce the amount of data that needs be transferred in subsequent request 518. A shortcut token can be an index value, database query information, file name, other pointer data, or an arbitrary value generated by the web site 503 and used to reference the stored user profile data.
A web server's public key file may be sent to the proxy server 502 using a security level specified by the site 503. For example, a web site's public key file include data indicating that the web site will use a specified one of the following shortcut key security levels:
none: If "none" is specified, the shortcut token is sent to the proxy server as a clear (e.g., unencrypted value).
low: If "low" is specified, the shortcut token is sent to the proxy server as a clear value and is accompanied by a hash of a previously requested URL.
medium: If "medium" is specified, the "low" security level information is further accompanied by a timestamp value.
high: If "high" is specified, the "medium" security information is further accompanied by the proxy server's IP address.
max: If "max" is specified, the "high" security information is further accompanied by a sequence counter value. The sequence counter value may be based on a initial URL hash, the key mask, or other value, and is incremented in subsequent transactions.
At low, medium, high, and max security levels, the shortcut token and related security data can be sent in encrypted form using, for example, the proxy server's public key (which may be the master key value). Shortcut token security levels may also be indicated using HTTP fields in a response 513 or 515, or may be specified using data stored in a configuration database at the proxy server 513 using a data entry terminal.
A proxy server 502 or web server 503 may include other HTTP fields in a request 512, 514, 518 or in a response 513, 515, 519 to control user profile data transfers and/or the operation of the SecureData protocol. For example, HTTP fields in requests and/or responses may specify the following directives:
Flush = <shortcut value I ALL>: The `Flush' directive can be sent to the proxy server 502 to discard a specified shortcut token or to discard all shortcut tokens from a particular web server. The `Flush' directive may also be sent to a web server to cause the web server to discard stored user profile data associated with a particular shortcut token or to discard all stored user profile data associated with the sending proxy server. This directive may be used by a web server 503 or proxy server 502 that is performing a reset operation.
WrongKey: The WrongKey directive indicate that improper security protocol information was received. A proxy server that receives the WrongKey directive may re-send a request using a HTTP "no-cache" pragma. The "no-cache" pragma indicates that cached data should not be used to satisfy the request.
medium: If "medium" is specified, the "low" security level information is further accompanied by a timestamp value.
high: If "high" is specified, the "medium" security information is further accompanied by the proxy server's IP address.
max: If "max" is specified, the "high" security information is further accompanied by a sequence counter value. The sequence counter value may be based on a initial URL hash, the key mask, or other value, and is incremented in subsequent transactions.
At low, medium, high, and max security levels, the shortcut token and related security data can be sent in encrypted form using, for example, the proxy server's public key (which may be the master key value). Shortcut token security levels may also be indicated using HTTP fields in a response 513 or 515, or may be specified using data stored in a configuration database at the proxy server 513 using a data entry terminal.
A proxy server 502 or web server 503 may include other HTTP fields in a request 512, 514, 518 or in a response 513, 515, 519 to control user profile data transfers and/or the operation of the SecureData protocol. For example, HTTP fields in requests and/or responses may specify the following directives:
Flush = <shortcut value I ALL>: The `Flush' directive can be sent to the proxy server 502 to discard a specified shortcut token or to discard all shortcut tokens from a particular web server. The `Flush' directive may also be sent to a web server to cause the web server to discard stored user profile data associated with a particular shortcut token or to discard all stored user profile data associated with the sending proxy server. This directive may be used by a web server 503 or proxy server 502 that is performing a reset operation.
WrongKey: The WrongKey directive indicate that improper security protocol information was received. A proxy server that receives the WrongKey directive may re-send a request using a HTTP "no-cache" pragma. The "no-cache" pragma indicates that cached data should not be used to satisfy the request.
SendFull: A web server can issue a SendFull directive to indicate that a proxy server should send "full" user profile data (rather than a shortcut token) in a subsequent HTTP
request.
TTL = <n>: The TTL (time to live) directive specifies a period (n, in seconds) during which a shortcut token is valid. Similar directives may be included in requests or response to indicate time-to-live values for other data, such as session keys and public keys.
The invention may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Apparatus of the invention may be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor; and method steps of the invention may be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output. The invention may advantageously be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device:
Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
A number of embodiments of the present invention have been described.
Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, server, proxy, and client protocols need not use the HTTP protocol. Alternate protocols and data formats may be used such as file transfer protocol (FTP) or network news transfer protocol (NNTP).
Accordingly, other embodiments are within the scope of the following claims.
request.
TTL = <n>: The TTL (time to live) directive specifies a period (n, in seconds) during which a shortcut token is valid. Similar directives may be included in requests or response to indicate time-to-live values for other data, such as session keys and public keys.
The invention may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Apparatus of the invention may be implemented in a computer program product tangibly embodied in a machine-readable storage device for execution by a programmable processor; and method steps of the invention may be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output. The invention may advantageously be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device:
Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language. Suitable processors include, by way of example, both general and special purpose microprocessors. Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing may be supplemented by, or incorporated in, specially-designed ASICs (application-specific integrated circuits).
A number of embodiments of the present invention have been described.
Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. For example, server, proxy, and client protocols need not use the HTTP protocol. Alternate protocols and data formats may be used such as file transfer protocol (FTP) or network news transfer protocol (NNTP).
Accordingly, other embodiments are within the scope of the following claims.
Claims (49)
1. A data transfer method performed by a proxy server, the method comprising:
intercepting an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determining an identity of a user of the client computer in response to receiving the HTTP request;
accessing a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers;
retrieving an identifier from the accessed storage based on the identity of the user;
inserting an additional field into the HTTP
request to create a modified HTTP request, the additional field containing the retrieved identifier;
sending the modified HTTP request to the HTTP
server such that the HTTP server parses the modified HTTP
request to extract the retrieved identifier, uses the retrieved identifier to retrieve the user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP
response to the proxy server;
receiving the HTTP response from the HTTP server;
and forwarding the HTTP response to the client computer.
intercepting an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determining an identity of a user of the client computer in response to receiving the HTTP request;
accessing a storage associated with the proxy server, the storage storing identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers;
retrieving an identifier from the accessed storage based on the identity of the user;
inserting an additional field into the HTTP
request to create a modified HTTP request, the additional field containing the retrieved identifier;
sending the modified HTTP request to the HTTP
server such that the HTTP server parses the modified HTTP
request to extract the retrieved identifier, uses the retrieved identifier to retrieve the user profile information from a storage associated with the HTTP server, generate an HTTP response to the HTTP request based on the retrieved user profile information, and sends the HTTP
response to the proxy server;
receiving the HTTP response from the HTTP server;
and forwarding the HTTP response to the client computer.
2. The method of claim 1 further comprising:
receiving an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determining an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieving user profile information based on the identity of the user;
encrypting the user profile information;
inserting an additional field into the initial HTTP request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP
request contains the encrypted user profile information;
sending the modified initial HTTP request to the HTTP server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receiving the identifier from the HTTP server;
storing the identifier in the storage associated with the proxy server;
receiving the initial HTTP response from the initial HTTP server; and forwarding the initial HTTP response to the client computer.
receiving an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determining an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieving user profile information based on the identity of the user;
encrypting the user profile information;
inserting an additional field into the initial HTTP request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP
request contains the encrypted user profile information;
sending the modified initial HTTP request to the HTTP server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receiving the identifier from the HTTP server;
storing the identifier in the storage associated with the proxy server;
receiving the initial HTTP response from the initial HTTP server; and forwarding the initial HTTP response to the client computer.
3. The method of claim 2 wherein encrypting the user profile information comprises determining a session key and using the session key to encrypt the user profile information.
4. The method of claim 3 further comprising:
encrypting the session key; and inserting a second additional field into the initial HTTP request to create the modified initial HTTP
request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
encrypting the session key; and inserting a second additional field into the initial HTTP request to create the modified initial HTTP
request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
5. The method of claim 4 wherein:
using the session key to encrypt the profile information comprises using the session key and a symmetric encryption algorithm to encrypt the user profile information, and encrypting the session key comprises encrypting the session key using a public key encryption algorithm and a public key associated with the HTTP server.
using the session key to encrypt the profile information comprises using the session key and a symmetric encryption algorithm to encrypt the user profile information, and encrypting the session key comprises encrypting the session key using a public key encryption algorithm and a public key associated with the HTTP server.
6. The method of claim 5 further comprising obtaining the public key from the HTTP server.
7. The method of claim 6 wherein obtaining the public key from the HTTP server comprises sending a request to the HTTP server to retrieve the public key.
8. The method of claim 3 wherein determining the session key comprises combining a master session key with a key mask.
9. The method of claim 1 wherein determining the identity of the user comprises:
determining an IP address of the client computer;
and querying a database to determine an identity associated with the IP address in the database.
determining an IP address of the client computer;
and querying a database to determine an identity associated with the IP address in the database.
10. The method of claim 2 further comprising determining that the HTTP server should receive the user profile information.
11. The method of claim 10 wherein determining that the HTTP server should receive the user profile information includes querying a database associated with the proxy server to determine if the HTTP server should receive the user profile information.
12. The method of claim 1 wherein determining the identity of the user comprises using the Internet Engineering Task Force IDENT protocol to determine the identity of the user.
13. The method of claim 1 wherein the user profile information comprises one or more of demographic information, a history of data requests by a user, age of a user, gender of a user, or interests of a user.
14. The method of claim 1 further comprising sending a flush directive to the HTTP server such that the HTTP server discards the user profile information stored in the storage associated with the HTTP server.
15. A data processing method performed by an HTTP
server, the method comprising:
receiving a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parsing the modified HTTP request to extract the identifier;
using the extracted identifier to retrieve user profile information from a storage associated with the HTTP
server;
generating an HTTP response to the HTTP request based on the retrieved user profile information; and sending the HTTP response to the proxy server for delivery to a client computer.
server, the method comprising:
receiving a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parsing the modified HTTP request to extract the identifier;
using the extracted identifier to retrieve user profile information from a storage associated with the HTTP
server;
generating an HTTP response to the HTTP request based on the retrieved user profile information; and sending the HTTP response to the proxy server for delivery to a client computer.
16. The method of claim 15 further comprising:
receiving an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP request contains encrypted user profile information;
parsing the initial modified HTTP request to extract the encrypted user profile information;
decrypting the encrypted user profile information extracted from the initial modified HTTP request;
generating an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
sending the initial HTTP response to the proxy server for delivery to a client computer;
storing the decrypted user profile information in the storage associated with the HTTP server;
generating the identifier; and sending the identifier to the proxy server.
receiving an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP request contains encrypted user profile information;
parsing the initial modified HTTP request to extract the encrypted user profile information;
decrypting the encrypted user profile information extracted from the initial modified HTTP request;
generating an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
sending the initial HTTP response to the proxy server for delivery to a client computer;
storing the decrypted user profile information in the storage associated with the HTTP server;
generating the identifier; and sending the identifier to the proxy server.
17. The method of claim 16 wherein generating an initial HTTP response to the initial HTTP request based on the decrypted user profile information comprises providing the decrypted user profile information to a web application.
18. The method of claim 17 wherein the web application comprises a common gateway interface script and providing the decrypted user profile information to the web application comprises setting HTTP environment variables accessible to the common gateway interface script.
19. The method of claim 16 wherein the initial modified HTTP request includes a second field inserted into the initial HTTP request by the proxy server, wherein the second field inserted into the initial HTTP request contains a session key, and decrypting the encrypted user profile information comprises decrypting the encrypted user profile information extracted from the initial modified HTTP request using the session key.
20. The method of claim 19 further comprising decrypting the session key.
21. The method of claim 20 wherein:
decrypting the session key comprises decrypting the session key using a public key algorithm and a private key of the HTTP server, and decrypting the encrypted user profile information using the session key comprises decrypting the encrypted user profile information using a symmetric decryption algorithm and the session key.
decrypting the session key comprises decrypting the session key using a public key algorithm and a private key of the HTTP server, and decrypting the encrypted user profile information using the session key comprises decrypting the encrypted user profile information using a symmetric decryption algorithm and the session key.
22. The method of claim 15 wherein the user profile information comprises one or more of demographic information, a history of data requests by a user, age of a user, gender of a user, or interests of a user.
23. The method of claim 15 further comprising:
receiving a flush directive from the proxy server;
and in response to receiving the flush directive, discarding the user profile information stored in the local storage.
receiving a flush directive from the proxy server;
and in response to receiving the flush directive, discarding the user profile information stored in the local storage.
24. A computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing a proxy server to:
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the HTTP request;
access a storage associated with the proxy server, the storage storing identifiers for use by HTTP servers in retrieving user profile information stored in storages associated with the HTTP servers;
retrieve an identifier from the accessed storage based on the identity of the user;
insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier;
send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP
response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server;
receive the HTTP response from the HTTP server;
and forward the HTTP response to the client computer.
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the HTTP request;
access a storage associated with the proxy server, the storage storing identifiers for use by HTTP servers in retrieving user profile information stored in storages associated with the HTTP servers;
retrieve an identifier from the accessed storage based on the identity of the user;
insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier;
send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP
response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server;
receive the HTTP response from the HTTP server;
and forward the HTTP response to the client computer.
25. The medium of claim 24 wherein the computer program further comprises instructions for causing the proxy server to:
receive an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieve user profile information based on the identity of the user;
encrypt the user profile information;
insert an additional field into the initial HTTP
request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP request contains the encrypted user profile information;
send the modified initial HTTP request to the HTTP
server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receive the identifier from the HTTP server;
store the identifier in the storage associated with the proxy server;
receive the initial HTTP response from the initial HTTP server; and forward the initial HTTP response to the client computer.
receive an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieve user profile information based on the identity of the user;
encrypt the user profile information;
insert an additional field into the initial HTTP
request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP request contains the encrypted user profile information;
send the modified initial HTTP request to the HTTP
server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receive the identifier from the HTTP server;
store the identifier in the storage associated with the proxy server;
receive the initial HTTP response from the initial HTTP server; and forward the initial HTTP response to the client computer.
26. The medium of claim 25 wherein, to encrypt the user profile information, the computer program further comprises instructions for causing the proxy server to determine a session key and using the session key to encrypt the user profile information.
27. The medium of claim 26 wherein the computer program further comprises instructions for causing the proxy server to:
encrypt the session key; and insert a second additional field into the initial HTTP request to create the modified initial HTTP request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
encrypt the session key; and insert a second additional field into the initial HTTP request to create the modified initial HTTP request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
28. The medium of claim 27 wherein:
to use the session key to encrypt the profile information, the computer program further comprises instructions for causing the proxy server to use the session key and a symmetric encryption algorithm to encrypt the user profile information, and to encrypt the session key, the computer program further comprises instructions for causing the proxy server to encrypt the session key using a public key encryption algorithm and a public key associated with the HTTP server.
to use the session key to encrypt the profile information, the computer program further comprises instructions for causing the proxy server to use the session key and a symmetric encryption algorithm to encrypt the user profile information, and to encrypt the session key, the computer program further comprises instructions for causing the proxy server to encrypt the session key using a public key encryption algorithm and a public key associated with the HTTP server.
29. The medium of claim 26 wherein, to determine the session key, the computer program further comprises instructions for causing the proxy server to combine a master session key with a key mask.
30. The medium of claim 24 wherein the user profile information comprises one or more of demographic information, a history of data requests by a user, age of a user, gender of a user, or interests of a user.
31. The medium of claim 24 wherein the computer program further comprises instructions for causing the proxy server to send a flush directive to the HTTP server such that the HTTP server discards the user profile information stored in the storage associated with the HTTP server.
32. A computer-usable medium having a computer program embodied thereon, the computer program comprising instructions for causing an HTTP server to:
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from a storage associated with the HTTP
server;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from a storage associated with the HTTP
server;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
33. The medium of claim 32 wherein the computer program further comprises instructions for causing the HTTP
server to:
receive an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP
request contains encrypted user profile information;
parse the initial modified HTTP request to extract the encrypted user profile information;
decrypt the encrypted user profile information extracted from the initial modified HTTP request;
generate an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
send the initial HTTP response to the proxy server for delivery to a client computer;
store the decrypted user profile information in the storage associated with the HTTP server;
generate the identifier; and send the identifier to the proxy server.
server to:
receive an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP
request contains encrypted user profile information;
parse the initial modified HTTP request to extract the encrypted user profile information;
decrypt the encrypted user profile information extracted from the initial modified HTTP request;
generate an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
send the initial HTTP response to the proxy server for delivery to a client computer;
store the decrypted user profile information in the storage associated with the HTTP server;
generate the identifier; and send the identifier to the proxy server.
34. The medium of claim 33 wherein the initial modified HTTP request includes a second field inserted into the initial HTTP request by the proxy server, wherein the second field inserted into the initial HTTP request contains a session key, and to decrypt the encrypted user profile information, the computer program further comprises instructions for causing the HTTP server to decrypt the encrypted user profile information extracted from the initial modified HTTP
request using the session key.
request using the session key.
35. The medium of claim 34 wherein the computer program further comprises instructions for causing the HTTP
server to decrypt the session key.
server to decrypt the session key.
36. The medium of claim 35 wherein:
to decrypt the session key, the computer program further comprises instructions for causing the HTTP server to decrypt the session key using a public key algorithm and a private key of the HTTP server, and to decrypt the encrypted user profile information using the session key, the computer program further comprises instructions for causing the HTTP server to decrypt the encrypted user profile information using a symmetric decryption algorithm and the session key.
to decrypt the session key, the computer program further comprises instructions for causing the HTTP server to decrypt the session key using a public key algorithm and a private key of the HTTP server, and to decrypt the encrypted user profile information using the session key, the computer program further comprises instructions for causing the HTTP server to decrypt the encrypted user profile information using a symmetric decryption algorithm and the session key.
37. The medium of claim 32 wherein the user profile information comprises one or more of demographic information, a history of data requests by a user, age of a user, gender of a user, or interests of a user.
38. The medium of claim 32 wherein the computer program further comprises instructions for causing the proxy server to:
receive a flush directive from the proxy server;
and discard the user profile information stored in the local storage.
receive a flush directive from the proxy server;
and discard the user profile information stored in the local storage.
39. A proxy server comprising:
a storage to store identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers;
a network interface operatively coupled to a network to exchange data with a client computer and with the HTTP server; and a processor operatively coupled to the network interface, the storage, and a memory comprising executable instructions for causing the processor to:
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the HTTP request;
retrieve an identifier from the storage based on the identity of the user;
insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier;
send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP
response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server;
receive the HTTP response from the HTTP server;
and forward the HTTP response to the client computer.
a storage to store identifiers for use by HTTP
servers in retrieving user profile information stored in storages associated with the HTTP servers;
a network interface operatively coupled to a network to exchange data with a client computer and with the HTTP server; and a processor operatively coupled to the network interface, the storage, and a memory comprising executable instructions for causing the processor to:
intercept an HTTP request from a client computer that is directed to an HTTP server, wherein the HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the HTTP request;
retrieve an identifier from the storage based on the identity of the user;
insert an additional field into the HTTP request to create a modified HTTP request, the additional field containing the retrieved identifier;
send the modified HTTP request to the HTTP server such that the HTTP server parses the modified HTTP request to extract the retrieved identifier, uses the retrieved identifier to retrieve user profile information from a storage associated with the HTTP server, generate an HTTP
response to the HTTP request based on the retrieved user profile information, and sends the HTTP response to the proxy server;
receive the HTTP response from the HTTP server;
and forward the HTTP response to the client computer.
40. The proxy server of claim 39 wherein the memory further comprises executable instructions for causing the processor to:
receive an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieve user profile information based on the identity of the user;
encrypt the user profile information;
insert an additional field into the initial HTTP
request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP request contains the encrypted user profile information;
send the modified initial HTTP request to the HTTP
server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receive the identifier from the HTTP server;
store the identifier in the storage associated with the proxy server;
receive the initial HTTP response from the HTTP
server; and forward the initial HTTP response to the client computer.
receive an initial HTTP request from the client computer that is directed to the HTTP server, wherein the initial HTTP request comprises a plurality of fields;
determine an identity of a user of the client computer in response to receiving the initial HTTP request;
retrieve user profile information based on the identity of the user;
encrypt the user profile information;
insert an additional field into the initial HTTP
request to create a modified initial HTTP request, wherein the additional field inserted into the initial HTTP request contains the encrypted user profile information;
send the modified initial HTTP request to the HTTP
server such that the HTTP server parses the modified initial HTTP request to extract and decrypt the encrypted user profile information, stores the decrypted user profile information in the storage associated with the HTTP server, generates an initial HTTP response to the initial HTTP
request based on the decrypted user profile information, generates the identifier, and sends the initial HTTP
response and the identifier to the proxy server;
receive the identifier from the HTTP server;
store the identifier in the storage associated with the proxy server;
receive the initial HTTP response from the HTTP
server; and forward the initial HTTP response to the client computer.
41. The proxy server of claim 40 wherein, to encrypt the user profile information, the memory further comprises executable instructions for causing the processor to determine a session key and using the session key to encrypt the user profile information.
42. The proxy server of claim 41 wherein the memory further comprises executable instructions for causing the processor to:
encrypt the session key; and insert a second additional field into the initial HTTP request to create the modified initial HTTP request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
encrypt the session key; and insert a second additional field into the initial HTTP request to create the modified initial HTTP request, wherein the second additional field inserted into the initial HTTP request contains the encrypted session key.
43. The proxy server of claim 42 wherein:
to use the session key to encrypt the profile information, the memory further comprises executable instructions for causing the processor to use the session key and a symmetric encryption algorithm to encrypt the user profile information, and to encrypt the session key, the memory further comprises executable instructions for causing the processor to encrypt the session key using a public key encryption algorithm and a public key associated with the HTTP server.
to use the session key to encrypt the profile information, the memory further comprises executable instructions for causing the processor to use the session key and a symmetric encryption algorithm to encrypt the user profile information, and to encrypt the session key, the memory further comprises executable instructions for causing the processor to encrypt the session key using a public key encryption algorithm and a public key associated with the HTTP server.
44. The proxy server of claim 41 wherein, to determine the session key, the memory further comprises executable instructions for causing the processor to combine a master session key with a key mask.
45. An HTTP server comprising:
a storage to store user profile information;
a network interface operatively coupled to a network to exchange data with a proxy server; and a processor operatively coupled to the network interface and a memory comprising executable instructions for causing the processor to:
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from the storage;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
a storage to store user profile information;
a network interface operatively coupled to a network to exchange data with a proxy server; and a processor operatively coupled to the network interface and a memory comprising executable instructions for causing the processor to:
receive a modified HTTP request from a proxy server, wherein the proxy server created the modified HTTP
request by inserting a field into an HTTP request intercepted by the proxy server, the inserted field containing an identifier;
parse the modified HTTP request to extract the identifier;
use the extracted identifier to retrieve user profile information from the storage;
generate an HTTP response to the HTTP request based on the retrieved user profile information; and send the HTTP response to the proxy server for delivery to a client computer.
46. The HTTP server of claim 45 wherein the memory further comprises executable instructions for causing the processor to:
receive an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP request contains encrypted user profile information;
parse the initial modified HTTP request to extract the encrypted user profile information;
decrypt the encrypted user profile information extracted from the initial modified HTTP request;
generate an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
send the initial HTTP response to the proxy server for delivery to a client computer;
store the decrypted user profile information in the storage;
generate the identifier; and send the identifier to the proxy server.
receive an initial modified HTTP request from a proxy server, wherein the initial modified HTTP request includes a field inserted into an initial HTTP request by the proxy server, wherein the field inserted into the initial HTTP request contains encrypted user profile information;
parse the initial modified HTTP request to extract the encrypted user profile information;
decrypt the encrypted user profile information extracted from the initial modified HTTP request;
generate an initial HTTP response to the initial HTTP request based on the decrypted user profile information;
send the initial HTTP response to the proxy server for delivery to a client computer;
store the decrypted user profile information in the storage;
generate the identifier; and send the identifier to the proxy server.
47. The HTTP sever of claim 46 wherein the initial modified HTTP request includes a second field inserted into the initial HTTP request by the proxy server, wherein the second field inserted into the initial HTTP request contains a session key, and to decrypt the encrypted user profile information, the memory further comprises executable instructions for causing the processor to decrypt the encrypted user profile information extracted from the initial modified HTTP request using the session key.
48. The HTTP server of claim 47 wherein the memory further comprises executable instructions for causing the processor to decrypt the session key.
49. The HTTP server of claim 48 wherein:
to decrypt the session key, the memory further comprises executable instructions for causing the processor to decrypt the session key using a public key algorithm and a private key of the HTTP server, and to decrypt the encrypted user profile information using the session key, the memory further comprises executable instructions for causing the processor to decrypt the encrypted user profile information using a symmetric decryption algorithm and the session key.
to decrypt the session key, the memory further comprises executable instructions for causing the processor to decrypt the session key using a public key algorithm and a private key of the HTTP server, and to decrypt the encrypted user profile information using the session key, the memory further comprises executable instructions for causing the processor to decrypt the encrypted user profile information using a symmetric decryption algorithm and the session key.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/323,415 | 1999-06-01 | ||
US09/323,415 US7146505B1 (en) | 1999-06-01 | 1999-06-01 | Secure data exchange between date processing systems |
PCT/US2000/015050 WO2000073876A2 (en) | 1999-06-01 | 2000-06-01 | Secure data exchange between data processing systems |
Publications (2)
Publication Number | Publication Date |
---|---|
CA2375443A1 CA2375443A1 (en) | 2000-12-07 |
CA2375443C true CA2375443C (en) | 2009-05-05 |
Family
ID=23259119
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002375443A Expired - Fee Related CA2375443C (en) | 1999-06-01 | 2000-06-01 | Secure data exchange between data processing systems |
Country Status (6)
Country | Link |
---|---|
US (9) | US7146505B1 (en) |
EP (1) | EP1181799A2 (en) |
JP (1) | JP2003501715A (en) |
AU (1) | AU5311000A (en) |
CA (1) | CA2375443C (en) |
WO (1) | WO2000073876A2 (en) |
Families Citing this family (169)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8601050B2 (en) | 1996-06-12 | 2013-12-03 | Michael Carringer | System and method for generating a modified web page by inline code insertion in response to an information request from a client computer |
US9130765B1 (en) * | 1996-06-12 | 2015-09-08 | Michael Carringer | System and method for generating a modified web page by inline code insertion in response to an information request from a client computer |
AU6410699A (en) | 1998-10-13 | 2000-05-01 | Chris Cheah | Method and system for controlled distribution of information over a network |
US7146505B1 (en) | 1999-06-01 | 2006-12-05 | America Online, Inc. | Secure data exchange between date processing systems |
US6678731B1 (en) * | 1999-07-08 | 2004-01-13 | Microsoft Corporation | Controlling access to a network server using an authentication ticket |
US7346695B1 (en) | 2002-10-28 | 2008-03-18 | F5 Networks, Inc. | System and method for performing application level persistence |
US7401115B1 (en) | 2000-10-23 | 2008-07-15 | Aol Llc | Processing selected browser requests |
US7493655B2 (en) * | 2000-03-22 | 2009-02-17 | Comscore Networks, Inc. | Systems for and methods of placing user identification in the header of data packets usable in user demographic reporting and collecting usage data |
US7930285B2 (en) * | 2000-03-22 | 2011-04-19 | Comscore, Inc. | Systems for and methods of user demographic reporting usable for identifying users and collecting usage data |
US7260837B2 (en) * | 2000-03-22 | 2007-08-21 | Comscore Networks, Inc. | Systems and methods for user identification, user demographic reporting and collecting usage data usage biometrics |
US7181412B1 (en) * | 2000-03-22 | 2007-02-20 | Comscore Networks Inc. | Systems and methods for collecting consumer data |
US9514459B1 (en) * | 2000-03-24 | 2016-12-06 | Emc Corporation | Identity broker tools and techniques for use with forward proxy computers |
US7962603B1 (en) * | 2000-06-06 | 2011-06-14 | Nobuyoshi Morimoto | System and method for identifying individual users accessing a web site |
US7032031B2 (en) * | 2000-06-23 | 2006-04-18 | Cloudshield Technologies, Inc. | Edge adapter apparatus and method |
US9444785B2 (en) | 2000-06-23 | 2016-09-13 | Cloudshield Technologies, Inc. | Transparent provisioning of network access to an application |
US8204082B2 (en) | 2000-06-23 | 2012-06-19 | Cloudshield Technologies, Inc. | Transparent provisioning of services over a network |
US7003555B1 (en) | 2000-06-23 | 2006-02-21 | Cloudshield Technologies, Inc. | Apparatus and method for domain name resolution |
US6829654B1 (en) * | 2000-06-23 | 2004-12-07 | Cloudshield Technologies, Inc. | Apparatus and method for virtual edge placement of web sites |
US20020083178A1 (en) * | 2000-08-11 | 2002-06-27 | Brothers John David West | Resource distribution in network environment |
WO2002067545A2 (en) * | 2001-02-17 | 2002-08-29 | Inktomi Corporation | Content based billing |
KR20030012877A (en) * | 2001-04-13 | 2003-02-12 | 코닌클리케 필립스 일렉트로닉스 엔.브이. | Speaker verification in a spoken dialogue system |
DE60100317T2 (en) * | 2001-07-12 | 2004-04-29 | Castify Networks S.A., Valbonne | Method for providing customer access to a content-providing server under the control of a resource-localizing server |
US7096490B2 (en) * | 2002-03-20 | 2006-08-22 | Actiontec Electronics, Inc. | Information routing device having an auto-configuration feature |
US8335915B2 (en) * | 2002-05-14 | 2012-12-18 | Netapp, Inc. | Encryption based security system for network storage |
US7187681B1 (en) * | 2002-06-11 | 2007-03-06 | Cisco Technology, Inc. | Method and apparatus for traffic quality and billing authorization by request token insertion |
US7461120B1 (en) * | 2002-07-09 | 2008-12-02 | Vignette Corporation | Method and system for identifying a visitor at a website server by requesting additional characteristic of a visitor computer from a visitor server |
US20040010710A1 (en) * | 2002-07-10 | 2004-01-15 | Wen-Hao Hsu | Method and system for filtering requests to a web site |
DE10241974B4 (en) * | 2002-09-11 | 2006-01-05 | Kämper, Peter | Monitoring of data transmissions |
GB0230329D0 (en) * | 2002-12-31 | 2003-02-05 | British Telecomm | Device profile generation |
US7403995B2 (en) * | 2003-01-08 | 2008-07-22 | Outhink, Inc. | Symmetrical bi-directional communication |
EP1453271B1 (en) * | 2003-02-28 | 2018-05-30 | Telefonaktiebolaget LM Ericsson (publ) | Device-type authentication in communication systems |
US7499914B2 (en) | 2003-04-04 | 2009-03-03 | Yahoo! Inc. | Search system using search subdomain and hints to subdomains in search query statements and sponsored results on a subdomain-by-subdomain basis |
US8473620B2 (en) * | 2003-04-14 | 2013-06-25 | Riverbed Technology, Inc. | Interception of a cloud-based communication connection |
US7779345B2 (en) * | 2003-07-30 | 2010-08-17 | Aol Inc. | Reverse mapping method and apparatus for form filling |
JP2005128996A (en) * | 2003-09-30 | 2005-05-19 | Dainippon Printing Co Ltd | Information processing apparatus and system, and program |
DE10345454A1 (en) * | 2003-09-30 | 2005-04-28 | Infineon Technologies Ag | Private key generator for access to storage device e.g. chip card, has page pre-key calculating device and determines private key based on pre-key and word address |
US8010783B1 (en) * | 2004-04-15 | 2011-08-30 | Aol Inc. | Service provider invocation |
US20050238174A1 (en) * | 2004-04-22 | 2005-10-27 | Motorola, Inc. | Method and system for secure communications over a public network |
US7721340B2 (en) * | 2004-06-12 | 2010-05-18 | Microsoft Corporation | Registry protection |
US7559091B2 (en) * | 2004-06-12 | 2009-07-07 | Microsoft Corporation | Software obfuscation |
US7681229B1 (en) * | 2004-06-22 | 2010-03-16 | Novell, Inc. | Proxy authentication |
US20080313306A1 (en) * | 2004-12-22 | 2008-12-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and Arrangements for Caching Static Information for Packet Data Applications In Wireless Communication Systems |
US20060282884A1 (en) * | 2005-06-09 | 2006-12-14 | Ori Pomerantz | Method and apparatus for using a proxy to manage confidential information |
CA2510647A1 (en) * | 2005-06-23 | 2006-12-23 | Cognos Incorporated | Signing of web request |
US20090119504A1 (en) * | 2005-08-10 | 2009-05-07 | Riverbed Technology, Inc. | Intercepting and split-terminating authenticated communication connections |
US8438628B2 (en) * | 2005-08-10 | 2013-05-07 | Riverbed Technology, Inc. | Method and apparatus for split-terminating a secure network connection, with client authentication |
US8478986B2 (en) * | 2005-08-10 | 2013-07-02 | Riverbed Technology, Inc. | Reducing latency of split-terminated secure communication protocol sessions |
US8898452B2 (en) * | 2005-09-08 | 2014-11-25 | Netapp, Inc. | Protocol translation |
GB0519466D0 (en) | 2005-09-23 | 2005-11-02 | Scansafe Ltd | Network communications |
US8200971B2 (en) | 2005-09-23 | 2012-06-12 | Cisco Technology, Inc. | Method for the provision of a network service |
GB2430591B (en) * | 2005-09-23 | 2010-09-01 | Scansafe Ltd | Network communications |
US9055093B2 (en) * | 2005-10-21 | 2015-06-09 | Kevin R. Borders | Method, system and computer program product for detecting at least one of security threats and undesirable computer files |
US20070099634A1 (en) * | 2005-11-02 | 2007-05-03 | Tropos Networks, Inc. | Mesh network that provides location information |
US20090031426A1 (en) * | 2005-12-30 | 2009-01-29 | Stefano Dal Lago | Method and System for Protected Distribution of Digitalized Sensitive Information |
US8209548B2 (en) * | 2006-02-06 | 2012-06-26 | International Business Machines Corporation | Secure caching technique for shared distributed caches |
US8782393B1 (en) | 2006-03-23 | 2014-07-15 | F5 Networks, Inc. | Accessing SSL connection data by a third-party |
US20070226483A1 (en) * | 2006-03-24 | 2007-09-27 | Dennis Cox | System and method for storing and/or transmitting emulated network flows |
US8281123B2 (en) * | 2006-03-24 | 2012-10-02 | Intel Corporation | Apparatus and method for managing and protecting information during use of semi-trusted interfaces |
JP4983165B2 (en) * | 2006-09-05 | 2012-07-25 | ソニー株式会社 | COMMUNICATION SYSTEM AND COMMUNICATION METHOD, INFORMATION PROCESSING DEVICE AND METHOD, DEVICE, PROGRAM, AND RECORDING MEDIUM |
WO2008030549A2 (en) * | 2006-09-06 | 2008-03-13 | Sslnext Inc. | Method and system for providing authentication service for internet users |
US8245050B1 (en) | 2006-09-29 | 2012-08-14 | Netapp, Inc. | System and method for initial key establishment using a split knowledge protocol |
US8042155B1 (en) | 2006-09-29 | 2011-10-18 | Netapp, Inc. | System and method for generating a single use password based on a challenge/response protocol |
US8190905B1 (en) | 2006-09-29 | 2012-05-29 | Netapp, Inc. | Authorizing administrative operations using a split knowledge protocol |
US8424058B2 (en) * | 2006-12-07 | 2013-04-16 | Sap Ag | Security proxying for end-user applications |
US20080141141A1 (en) * | 2006-12-07 | 2008-06-12 | Moore Dennis B | Widget runtime engine for enterprise widgets |
US8117555B2 (en) * | 2006-12-07 | 2012-02-14 | Sap Ag | Cooperating widgets |
US20080215998A1 (en) * | 2006-12-07 | 2008-09-04 | Moore Dennis B | Widget launcher and briefcase |
DE602006015827D1 (en) * | 2006-12-08 | 2010-09-09 | Ubs Ag | Method and apparatus for detecting the IP address of a computer and related location information |
US8615562B1 (en) | 2006-12-29 | 2013-12-24 | Google Inc. | Proxy for tolerating faults in high-security systems |
US20080168065A1 (en) * | 2007-01-05 | 2008-07-10 | International Business Machines Corporation | System and Method for Universal Web-History Service in Single or Collaborative Environments |
US8862747B2 (en) * | 2007-03-10 | 2014-10-14 | Bridge And Post, Inc. | Method and apparatus for tagging network traffic using extensible fields in message headers |
US8190875B2 (en) * | 2007-03-22 | 2012-05-29 | Cisco Technology, Inc. | Reducing processing load in proxies for secure communications |
US8607046B1 (en) | 2007-04-23 | 2013-12-10 | Netapp, Inc. | System and method for signing a message to provide one-time approval to a plurality of parties |
US8611542B1 (en) | 2007-04-26 | 2013-12-17 | Netapp, Inc. | Peer to peer key synchronization |
US8824686B1 (en) | 2007-04-27 | 2014-09-02 | Netapp, Inc. | Cluster key synchronization |
US8782414B2 (en) * | 2007-05-07 | 2014-07-15 | Microsoft Corporation | Mutually authenticated secure channel |
US20080307035A1 (en) * | 2007-06-05 | 2008-12-11 | Erik John Burckart | System and Method for Off-loading Online Meeting Updates Using Forward Proxy |
US8196182B2 (en) | 2007-08-24 | 2012-06-05 | Netapp, Inc. | Distributed management of crypto module white lists |
US9774445B1 (en) | 2007-09-04 | 2017-09-26 | Netapp, Inc. | Host based rekeying |
US7752285B2 (en) | 2007-09-17 | 2010-07-06 | Yahoo! Inc. | Shortcut sets for controlled environments |
US9479599B2 (en) * | 2007-10-04 | 2016-10-25 | International Business Machines Corporation | Reroute of a web service in a web based application |
US9558097B2 (en) * | 2007-11-13 | 2017-01-31 | Red Hat, Inc. | Automated recording and playback of application interactions |
US8849944B2 (en) * | 2007-11-27 | 2014-09-30 | Red Hat, Inc. | Multi-use application proxy |
US8532303B2 (en) * | 2007-12-14 | 2013-09-10 | Intel Corporation | Symmetric key distribution framework for the internet |
US8365271B2 (en) * | 2008-02-27 | 2013-01-29 | International Business Machines Corporation | Controlling access of a client system to access protected remote resources supporting relative URLs |
WO2009148221A2 (en) * | 2008-06-04 | 2009-12-10 | 삼성전자 주식회사 | Method and device for transmitting and receiving filtered content in accordance with age restrictions |
US9003186B2 (en) * | 2008-07-24 | 2015-04-07 | Zscaler, Inc. | HTTP authentication and authorization management |
US9379895B2 (en) | 2008-07-24 | 2016-06-28 | Zscaler, Inc. | HTTP authentication and authorization management |
US8738683B2 (en) | 2008-09-15 | 2014-05-27 | Vaultive Ltd. | System, apparatus and method for encryption and decryption of data transmitted over a network |
CN102217225B (en) * | 2008-10-03 | 2014-04-02 | 杰出网络公司 | Content delivery network encryption |
US20110135093A1 (en) * | 2008-11-26 | 2011-06-09 | Radatti Peter V | Secure telephone devices, systems and methods |
US8693686B2 (en) * | 2008-11-26 | 2014-04-08 | Peter V. Radatti | Secure telephone devices, systems and methods |
US8990569B2 (en) * | 2008-12-03 | 2015-03-24 | Verizon Patent And Licensing Inc. | Secure communication session setup |
US8707043B2 (en) * | 2009-03-03 | 2014-04-22 | Riverbed Technology, Inc. | Split termination of secure communication sessions with mutual certificate-based authentication |
JP5293580B2 (en) | 2009-03-19 | 2013-09-18 | 日本電気株式会社 | Web service system, web service method and program |
US9652899B2 (en) * | 2009-04-09 | 2017-05-16 | Honeywell International Inc. | Methods, apparatus and systems for accessing vehicle operational data using an intelligent network router |
US9590990B2 (en) * | 2009-05-11 | 2017-03-07 | International Business Machines Corporation | Assigning user requests of different types or protocols to a user by trust association interceptors |
US8489685B2 (en) | 2009-07-17 | 2013-07-16 | Aryaka Networks, Inc. | Application acceleration as a service system and method |
US9668230B2 (en) * | 2009-11-10 | 2017-05-30 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Security integration between a wireless and a wired network using a wireless gateway proxy |
JP5424940B2 (en) * | 2010-03-03 | 2014-02-26 | キヤノン株式会社 | Network apparatus, information processing apparatus, control method thereof, network system, proxy response method, and computer program |
US8700892B2 (en) | 2010-03-19 | 2014-04-15 | F5 Networks, Inc. | Proxy SSL authentication in split SSL for client-side proxy agent resources with content insertion |
CA2800163A1 (en) * | 2010-05-21 | 2011-11-24 | Vaultive Ltd. | System and method for controlling and monitoring access to data processing applications |
US9235843B2 (en) * | 2010-09-27 | 2016-01-12 | T-Mobile Usa, Inc. | Insertion of user information into headers to enable targeted responses |
US8505083B2 (en) | 2010-09-30 | 2013-08-06 | Microsoft Corporation | Remote resources single sign on |
US20120124193A1 (en) | 2010-11-12 | 2012-05-17 | International Business Machines Corporation | Identification of Critical Web Services and their Dynamic Optimal Relocation |
EP2472820B1 (en) * | 2010-12-31 | 2016-04-20 | Regify S.A. | Network, node and method for anonymizing and routing a user request |
JP5939645B2 (en) * | 2011-03-25 | 2016-06-22 | 日本電気株式会社 | Information leakage prevention apparatus, method and program |
US9154815B2 (en) * | 2011-05-06 | 2015-10-06 | Disney Enterprises, Inc. | Method and system for securing multimedia data streamed over a network |
KR20130003616A (en) * | 2011-06-30 | 2013-01-09 | 한국전자통신연구원 | Apparatus and method for generating session key and cluster key |
US8782162B1 (en) * | 2011-07-20 | 2014-07-15 | Google Inc. | System for merging and comparing real-time analytics data with conventional analytics data |
US8782166B1 (en) * | 2011-07-20 | 2014-07-15 | Google Inc. | System for generating a site pathing report based on real-time analytics data |
US9203609B2 (en) * | 2011-12-12 | 2015-12-01 | Nokia Technologies Oy | Method and apparatus for implementing key stream hierarchy |
DE102012200042A1 (en) * | 2012-01-03 | 2013-07-04 | Airbus Operations Gmbh | SERVER SYSTEM, AIR OR ROOM VEHICLE AND METHOD |
US20130191882A1 (en) * | 2012-01-19 | 2013-07-25 | Sap Ag | Access control of remote communication interfaces based on system-specific keys |
US8914629B2 (en) * | 2012-01-30 | 2014-12-16 | The Nielsen Company (Us), Llc | Intercepting encrypted network traffic for internet usage monitoring |
KR101874119B1 (en) * | 2012-02-07 | 2018-07-03 | 삼성전자주식회사 | Authentication method between client and server, machine-readable storage medium, client and server |
US9930037B2 (en) | 2012-05-22 | 2018-03-27 | Verizon Patent And Licensing Inc. | Encrypting a unique identification header to create different transactional identifiers |
US9887872B2 (en) * | 2012-07-13 | 2018-02-06 | Microsoft Technology Licensing, Llc | Hybrid application environments including hosted applications and application servers for interacting with data in enterprise environments |
US9798695B2 (en) | 2012-08-07 | 2017-10-24 | Nokia Technologies Oy | Access control for wireless memory |
US9270760B2 (en) * | 2012-10-15 | 2016-02-23 | Google Inc. | Cross-platform child mode for applications |
US9998564B1 (en) * | 2012-11-07 | 2018-06-12 | Amazon Technologies, Inc. | Using custom protocol headers to modify non-header data |
US20140201045A1 (en) * | 2013-01-17 | 2014-07-17 | Yogish Pai | Determining local tax structures in an accounting application through user contribution |
US9549047B1 (en) * | 2013-03-14 | 2017-01-17 | Google Inc. | Initiating a client-side user model |
CN104065623B (en) * | 2013-03-21 | 2018-01-23 | 华为终端(东莞)有限公司 | Information processing method, trust server and Cloud Server |
US9866648B2 (en) * | 2013-05-10 | 2018-01-09 | Laurent Bortolamiol | Automatic transmission of user profile information to a web server |
KR102138315B1 (en) * | 2013-05-30 | 2020-07-27 | 삼성전자주식회사 | Method and Apparatus for Provisioning Profile |
US10108987B2 (en) * | 2013-06-21 | 2018-10-23 | Iheartmedia Management Services, Inc. | E-mail based dynamic advertising |
US9438568B2 (en) * | 2013-08-02 | 2016-09-06 | Zeva Incorporated | System and method for email and file decryption without direct access to required decryption key |
KR101434582B1 (en) | 2013-08-30 | 2014-08-27 | 삼성전자주식회사 | METHOD FOR KEY RECOVERY USING SRTCP CHANNEL IN VoIP SYSTEM AND APPARATUS THEREROF |
US9882884B1 (en) * | 2014-01-15 | 2018-01-30 | United States Automobile Association (USAA) | Authenticating mobile traffic |
US9270449B1 (en) * | 2014-01-17 | 2016-02-23 | Amazon Technologies, Inc. | Secured communication in network environments |
US10749926B2 (en) * | 2014-04-23 | 2020-08-18 | Rimini Street, Inc. | Proxy for modifying HTTP messages to comply with browser |
US9871849B2 (en) | 2014-05-20 | 2018-01-16 | Citrix Systems, Inc. | Systems and methods for just-in-time state sharing |
US9258117B1 (en) | 2014-06-26 | 2016-02-09 | Amazon Technologies, Inc. | Mutual authentication with symmetric secrets and signatures |
US9948610B2 (en) | 2014-08-29 | 2018-04-17 | Citrix Systems, Inc. | Method and apparatus for accessing third-party resources |
US10198558B2 (en) * | 2014-10-06 | 2019-02-05 | Red Hat, Inc. | Data source security cluster |
US9602992B2 (en) | 2015-01-21 | 2017-03-21 | Verizon Patent And Licensing Inc. | Adding a unique identification header to non-operator network communication |
EP3251319B1 (en) * | 2015-01-27 | 2019-11-20 | Telefonaktiebolaget LM Ericsson (publ) | Correlated personalization of multiple communication services |
US9372687B1 (en) * | 2015-05-29 | 2016-06-21 | Intuit Inc. | Product customization based on user contributions |
US10129220B2 (en) | 2015-06-13 | 2018-11-13 | Avocado Systems Inc. | Application and data protection tag |
US10193889B2 (en) | 2015-06-14 | 2019-01-29 | Avocado Systems Inc. | Data socket descriptor attributes for application discovery in data centers |
US10397277B2 (en) | 2015-06-14 | 2019-08-27 | Avocado Systems Inc. | Dynamic data socket descriptor mirroring mechanism and use for security analytics |
US10270810B2 (en) | 2015-06-14 | 2019-04-23 | Avocado Systems Inc. | Data socket descriptor based policies for application and data behavior and security |
US10122689B2 (en) | 2015-06-16 | 2018-11-06 | Amazon Technologies, Inc. | Load balancing with handshake offload |
US10122692B2 (en) | 2015-06-16 | 2018-11-06 | Amazon Technologies, Inc. | Handshake offload |
US10148697B2 (en) | 2015-06-16 | 2018-12-04 | Avocado Systems Inc. | Unified host based security exchange between heterogeneous end point security agents |
US10193930B2 (en) | 2015-06-29 | 2019-01-29 | Avocado Systems Inc. | Application security capability exchange via the application and data protection layer |
US10356068B2 (en) | 2015-07-14 | 2019-07-16 | Avocado Systems Inc. | Security key generator module for security sensitive applications |
US10354070B2 (en) | 2015-08-22 | 2019-07-16 | Avocado Systems Inc. | Thread level access control to socket descriptors and end-to-end thread level policies for thread protection |
WO2017074460A1 (en) * | 2015-10-30 | 2017-05-04 | Intuit Inc. | Selective encryption of profile fields for multiple consumers |
US10230701B2 (en) | 2015-10-30 | 2019-03-12 | Intuit Inc. | Selective encryption of profile fields for multiple consumers |
US10409780B1 (en) | 2015-10-30 | 2019-09-10 | Intuit, Inc. | Making a copy of a profile store while processing live updates |
WO2017139652A1 (en) * | 2016-02-10 | 2017-08-17 | MobileIron, Inc. | Securely storing and distributing sensitive data in a cloud-based application |
CN107231335B (en) * | 2016-03-24 | 2021-05-25 | 创新先进技术有限公司 | Service processing method and device |
CN107666383B (en) * | 2016-07-29 | 2021-06-18 | 阿里巴巴集团控股有限公司 | Message processing method and device based on HTTPS (hypertext transfer protocol secure protocol) |
US20180182270A1 (en) * | 2016-12-22 | 2018-06-28 | Hewlett-Packard Development Company, L.P. | Displays representative of remote subjects |
US10686606B2 (en) * | 2017-02-14 | 2020-06-16 | Facebook, Inc. | Header enhancement |
EP3404890B1 (en) | 2017-05-18 | 2022-08-24 | F. Hoffmann-La Roche AG | Methods and systems for processing data of an analytical instrument for analyzing biological samples |
US9948736B1 (en) * | 2017-07-10 | 2018-04-17 | Spotify Ab | System and method for providing real-time media consumption data |
CN107508839A (en) * | 2017-09-28 | 2017-12-22 | 中国银联股份有限公司 | A kind of method and apparatus for controlling web system unauthorized access |
US10637906B2 (en) | 2017-10-31 | 2020-04-28 | Cisco Technology, Inc. | Dynamic socket QoS settings for web service connections |
US10972580B1 (en) * | 2017-12-12 | 2021-04-06 | Amazon Technologies, Inc. | Dynamic metadata encryption |
EP4170970A1 (en) * | 2018-01-31 | 2023-04-26 | Cable Television Laboratories, Inc. | Systems and methods for privacy management using a digital ledger |
US20190340653A1 (en) * | 2018-05-02 | 2019-11-07 | Capital One Services, Llc | Method and System for Personalization of Advertisement Content |
CN109688196B (en) * | 2018-11-19 | 2020-04-10 | 北京三快在线科技有限公司 | Order state pushing method and device, electronic equipment and readable storage medium |
US11936630B1 (en) * | 2020-04-29 | 2024-03-19 | United Services Automobile Association (Usaa) | Systems and methods for establishing encrypted internet communication |
JP2023537440A (en) * | 2020-07-06 | 2023-09-01 | 株式会社メガチップス | Information processing equipment |
US11847483B2 (en) * | 2020-12-03 | 2023-12-19 | International Business Machines Corporation | Secure virtual machine software management |
US11716391B2 (en) * | 2020-12-17 | 2023-08-01 | Microsoft Technology Licensing, Llc | Encryption of proxy session activity data using user-provided encryption keys |
Family Cites Families (162)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4238853A (en) * | 1977-12-05 | 1980-12-09 | International Business Machines Corporation | Cryptographic communication security for single domain networks |
US4578530A (en) * | 1981-06-26 | 1986-03-25 | Visa U.S.A., Inc. | End-to-end encryption system and method of operation |
US5245656A (en) * | 1992-09-09 | 1993-09-14 | Bell Communications Research, Inc. | Security method for private information delivery and filtering in public networks |
US5586260A (en) | 1993-02-12 | 1996-12-17 | Digital Equipment Corporation | Method and apparatus for authenticating a client to a server in computer systems which support different security mechanisms |
US5944794A (en) | 1994-09-30 | 1999-08-31 | Kabushiki Kaisha Toshiba | User identification data management scheme for networking computer systems using wide area network |
US5724521A (en) * | 1994-11-03 | 1998-03-03 | Intel Corporation | Method and apparatus for providing electronic advertisements to end users in a consumer best-fit pricing manner |
US5758257A (en) | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
US5764890A (en) | 1994-12-13 | 1998-06-09 | Microsoft Corporation | Method and system for adding a secure network server to an existing computer network |
US5590197A (en) | 1995-04-04 | 1996-12-31 | V-One Corporation | Electronic payment system and method |
US5802320A (en) | 1995-05-18 | 1998-09-01 | Sun Microsystems, Inc. | System for packet filtering of data packets at a computer network interface |
US5678041A (en) | 1995-06-06 | 1997-10-14 | At&T | System and method for restricting user access rights on the internet based on rating information stored in a relational database |
US5708780A (en) | 1995-06-07 | 1998-01-13 | Open Market, Inc. | Internet server access control and monitoring systems |
US7272639B1 (en) * | 1995-06-07 | 2007-09-18 | Soverain Software Llc | Internet server access control and monitoring systems |
US5996019A (en) | 1995-07-19 | 1999-11-30 | Fujitsu Network Communications, Inc. | Network link access scheduling using a plurality of prioritized lists containing queue identifiers |
US5657390A (en) | 1995-08-25 | 1997-08-12 | Netscape Communications Corporation | Secure socket layer application program apparatus and method |
US5826025A (en) | 1995-09-08 | 1998-10-20 | Sun Microsystems, Inc. | System for annotation overlay proxy configured to retrieve associated overlays associated with a document request from annotation directory created from list of overlay groups |
US5812769A (en) | 1995-09-20 | 1998-09-22 | Infonautics Corporation | Method and apparatus for redirecting a user to a new location on the world wide web using relative universal resource locators |
DE29515574U1 (en) * | 1995-09-29 | 1995-11-30 | Schwan Stabilo Schwanhaeusser | Ring element |
US5774670A (en) | 1995-10-06 | 1998-06-30 | Netscape Communications Corporation | Persistent client state in a hypertext transfer protocol based client-server system |
US5740252A (en) * | 1995-10-13 | 1998-04-14 | C/Net, Inc. | Apparatus and method for passing private demographic information between hyperlink destinations |
JPH09114783A (en) | 1995-10-13 | 1997-05-02 | Sony Corp | Device and method for processing information |
WO1997015885A1 (en) | 1995-10-25 | 1997-05-01 | Open Market, Inc. | Managing transfers of information in a communications network |
US6029175A (en) | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
US6016319A (en) | 1995-10-31 | 2000-01-18 | Lucent Technologies, Inc. | Communications system for transmission of datagram packets over connection-oriented networks |
US5892761A (en) | 1995-10-31 | 1999-04-06 | Netscape Communications Corporation | Method and apparatus for routing data in collaborative computing system |
US5671279A (en) | 1995-11-13 | 1997-09-23 | Netscape Communications Corporation | Electronic commerce using a secure courier system |
US5794210A (en) | 1995-12-11 | 1998-08-11 | Cybergold, Inc. | Attention brokerage |
US6081829A (en) | 1996-01-31 | 2000-06-27 | Silicon Graphics, Inc. | General purpose web annotations without modifying browser |
US5826014A (en) | 1996-02-06 | 1998-10-20 | Network Engineering Software | Firewall system for protecting network elements connected to a public network |
US5673322A (en) * | 1996-03-22 | 1997-09-30 | Bell Communications Research, Inc. | System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks |
US5815665A (en) | 1996-04-03 | 1998-09-29 | Microsoft Corporation | System and method for providing trusted brokering services over a distributed network |
US5848396A (en) | 1996-04-26 | 1998-12-08 | Freedom Of Information, Inc. | Method and apparatus for determining behavioral profile of a computer user |
US6178411B1 (en) | 1996-05-28 | 2001-01-23 | Joshua J. Reiter | Interactive process for applying or printing information on letters or parcels |
US5740361A (en) | 1996-06-03 | 1998-04-14 | Compuserve Incorporated | System for remote pass-phrase authentication |
US5845300A (en) | 1996-06-05 | 1998-12-01 | Microsoft Corporation | Method and apparatus for suggesting completions for a partially entered data item based on previously-entered, associated data items |
US6373950B1 (en) * | 1996-06-17 | 2002-04-16 | Hewlett-Packard Company | System, method and article of manufacture for transmitting messages within messages utilizing an extensible, flexible architecture |
US5757925A (en) * | 1996-07-23 | 1998-05-26 | Faybishenko; Yaroslav | Secure platform independent cross-platform remote execution computer system and method |
US5933811A (en) | 1996-08-20 | 1999-08-03 | Paul D. Angles | System and method for delivering customized advertisements within interactive communication systems |
US5933827A (en) | 1996-09-25 | 1999-08-03 | International Business Machines Corporation | System for identifying new web pages of interest to a user |
US6092204A (en) | 1996-10-01 | 2000-07-18 | At&T Corp | Filtering for public databases with naming ambiguities |
US6047376A (en) | 1996-10-18 | 2000-04-04 | Toshiba Information Systems (Japan) Corporation | Client-server system, server access authentication method, memory medium stores server-access authentication programs, and issuance device which issues the memory medium contents |
US5905872A (en) | 1996-11-05 | 1999-05-18 | At&T Corp. | Method of transferring connection management information in world wideweb requests and responses |
US20020059402A1 (en) * | 1996-11-15 | 2002-05-16 | Charles E. Belanger | Server-sided internet-based platform independent operating system and application suite |
US5818446A (en) | 1996-11-18 | 1998-10-06 | International Business Machines Corporation | System for changing user interfaces based on display data content |
US20030036974A1 (en) * | 1996-12-03 | 2003-02-20 | Richard Allen | Apparatus and method for an on demand data delivery system for the preview selection, retrieval and reproduction at a remote location of previously recorded or programmed materials |
US6131095A (en) | 1996-12-11 | 2000-10-10 | Hewlett-Packard Company | Method of accessing a target entity over a communications network |
EP0848338A1 (en) | 1996-12-12 | 1998-06-17 | SONY DEUTSCHLAND GmbH | Server providing documents according to user profiles |
US5845070A (en) | 1996-12-18 | 1998-12-01 | Auric Web Systems, Inc. | Security system for internet provider transaction |
US6182141B1 (en) | 1996-12-20 | 2001-01-30 | Intel Corporation | Transparent proxy server |
KR20000070005A (en) | 1997-01-09 | 2000-11-25 | 코페이 스티븐 | Monitoring of remote file access on a public computer network |
US5961593A (en) * | 1997-01-22 | 1999-10-05 | Lucent Technologies, Inc. | System and method for providing anonymous personalized browsing by a proxy system in a network |
US6049821A (en) | 1997-01-24 | 2000-04-11 | Motorola, Inc. | Proxy host computer and method for accessing and retrieving information between a browser and a proxy |
US5978799A (en) | 1997-01-30 | 1999-11-02 | Hirsch; G. Scott | Search engine including query database, user profile database, information templates and email facility |
US6041357A (en) | 1997-02-06 | 2000-03-21 | Electric Classified, Inc. | Common session token system and protocol |
CA2692298C (en) | 1997-02-07 | 2014-10-28 | About.Com, Inc. | Collaborative internet data mining system |
US6128663A (en) | 1997-02-11 | 2000-10-03 | Invention Depot, Inc. | Method and apparatus for customization of information content provided to a requestor over a network using demographic information yet the user remains anonymous to the server |
US6138162A (en) | 1997-02-11 | 2000-10-24 | Pointcast, Inc. | Method and apparatus for configuring a client to redirect requests to a caching proxy server based on a category ID with the request |
US6301661B1 (en) | 1997-02-12 | 2001-10-09 | Verizon Labortories Inc. | Enhanced security for applications employing downloadable executable content |
US5923756A (en) | 1997-02-12 | 1999-07-13 | Gte Laboratories Incorporated | Method for providing secure remote command execution over an insecure computer network |
US5908469A (en) * | 1997-02-14 | 1999-06-01 | International Business Machines Corporation | Generic user authentication for network computers |
US6105027A (en) | 1997-03-10 | 2000-08-15 | Internet Dynamics, Inc. | Techniques for eliminating redundant access checking by access filters |
AU6777598A (en) | 1997-03-26 | 1998-10-20 | Davox Corporation | Browser user interface for client workstation |
US6266681B1 (en) | 1997-04-08 | 2001-07-24 | Network Commerce Inc. | Method and system for inserting code to conditionally incorporate a user interface component in an HTML document |
US6766454B1 (en) * | 1997-04-08 | 2004-07-20 | Visto Corporation | System and method for using an authentication applet to identify and authenticate a user in a computer network |
US5974398A (en) | 1997-04-11 | 1999-10-26 | At&T Corp. | Method and apparatus enabling valuation of user access of advertising carried by interactive information and entertainment services |
US5991795A (en) | 1997-04-18 | 1999-11-23 | Emware, Inc. | Communication system and methods using dynamic expansion for computer networks |
US6170017B1 (en) | 1997-05-08 | 2001-01-02 | International Business Machines Corporation | Method and system coordinating actions among a group of servers |
US6161145A (en) * | 1997-05-08 | 2000-12-12 | International Business Machines Corporation | Updating server-related data at a client |
US5805803A (en) | 1997-05-13 | 1998-09-08 | Digital Equipment Corporation | Secure web tunnel |
US6314565B1 (en) | 1997-05-19 | 2001-11-06 | Intervu, Inc. | System and method for automated identification, retrieval, and installation of multimedia software components |
US6151686A (en) | 1997-06-06 | 2000-11-21 | Fmr Corp. | Managing an information retrieval problem |
US5987454A (en) | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
US7039599B2 (en) | 1997-06-16 | 2006-05-02 | Doubleclick Inc. | Method and apparatus for automatic placement of advertising |
WO1999000958A1 (en) | 1997-06-26 | 1999-01-07 | British Telecommunications Plc | Data communications |
US6272631B1 (en) * | 1997-06-30 | 2001-08-07 | Microsoft Corporation | Protected storage of core data secrets |
AU3625097A (en) | 1997-07-08 | 1999-02-08 | France Telecom Interactive | System and method for managing transactions between service suppliers and customers on a communication network |
US6049877A (en) * | 1997-07-16 | 2000-04-11 | International Business Machines Corporation | Systems, methods and computer program products for authorizing common gateway interface application requests |
JP3220055B2 (en) | 1997-07-17 | 2001-10-22 | 松下電器産業株式会社 | An optimizing device for optimizing a machine language instruction sequence or an assembly language instruction sequence, and a compiler device for converting a source program described in a high-level language into a machine language or an assembly language instruction sequence. |
US6317795B1 (en) | 1997-07-22 | 2001-11-13 | International Business Machines Corporation | Dynamic modification of multimedia content |
US6760746B1 (en) | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US6006268A (en) | 1997-07-31 | 1999-12-21 | Cisco Technology, Inc. | Method and apparatus for reducing overhead on a proxied connection |
US5991810A (en) * | 1997-08-01 | 1999-11-23 | Novell, Inc. | User name authentication for gateway clients accessing a proxy cache server |
US6393407B1 (en) | 1997-09-11 | 2002-05-21 | Enliven, Inc. | Tracking user micro-interactions with web page advertising |
US5960411A (en) | 1997-09-12 | 1999-09-28 | Amazon.Com, Inc. | Method and system for placing a purchase order via a communications network |
US6112212A (en) | 1997-09-15 | 2000-08-29 | The Pangea Project Llc | Systems and methods for organizing and analyzing information stored on a computer network |
US7225249B1 (en) * | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
US6631402B1 (en) * | 1997-09-26 | 2003-10-07 | Worldcom, Inc. | Integrated proxy interface for web based report requester tool set |
US5941954A (en) | 1997-10-01 | 1999-08-24 | Sun Microsystems, Inc. | Network message redirection |
US6418471B1 (en) | 1997-10-06 | 2002-07-09 | Ncr Corporation | Method for recording and reproducing the browsing activities of an individual web browser |
US6512754B2 (en) | 1997-10-14 | 2003-01-28 | Lucent Technologies Inc. | Point-to-point protocol encapsulation in ethernet frame |
US6119098A (en) | 1997-10-14 | 2000-09-12 | Patrice D. Guyot | System and method for targeting and distributing advertisements over a distributed network |
US6308216B1 (en) * | 1997-11-14 | 2001-10-23 | International Business Machines Corporation | Service request routing using quality-of-service data and network resource information |
US6272492B1 (en) | 1997-11-21 | 2001-08-07 | Ibm Corporation | Front-end proxy for transparently increasing web server functionality |
US6052785A (en) * | 1997-11-21 | 2000-04-18 | International Business Machines Corporation | Multiple remote data access security mechanism for multitiered internet computer networks |
US6092196A (en) | 1997-11-25 | 2000-07-18 | Nortel Networks Limited | HTTP distributed remote user authentication system |
US6769019B2 (en) | 1997-12-10 | 2004-07-27 | Xavier Ferguson | Method of background downloading of information from a computer network |
US6286046B1 (en) | 1997-12-22 | 2001-09-04 | International Business Machines Corporation | Method of recording and measuring e-business sessions on the world wide web |
US9900305B2 (en) | 1998-01-12 | 2018-02-20 | Soverain Ip, Llc | Internet server access control and monitoring systems |
US6735631B1 (en) | 1998-02-10 | 2004-05-11 | Sprint Communications Company, L.P. | Method and system for networking redirecting |
US6357010B1 (en) | 1998-02-17 | 2002-03-12 | Secure Computing Corporation | System and method for controlling access to documents stored on an internal network |
US6038598A (en) | 1998-02-23 | 2000-03-14 | Intel Corporation | Method of providing one of a plurality of web pages mapped to a single uniform resource locator (URL) based on evaluation of a condition |
US6438592B1 (en) | 1998-02-25 | 2002-08-20 | Michael G. Killian | Systems for monitoring and improving performance on the world wide web |
ATE239260T1 (en) | 1998-02-27 | 2003-05-15 | Engage Technologies | SYSTEM AND METHOD FOR BUILDING USER PROFILES |
US6321336B1 (en) | 1998-03-13 | 2001-11-20 | Secure Computing Corporation | System and method for redirecting network traffic to provide secure communication |
US6128627A (en) | 1998-04-15 | 2000-10-03 | Inktomi Corporation | Consistent data storage in an object cache |
US6073175A (en) | 1998-04-27 | 2000-06-06 | International Business Machines Corporation | Method for supporting different service levels in a network using web page content information |
BRPI9910049B1 (en) * | 1998-04-28 | 2016-11-16 | Nokia Corp | method and network for controlling wireless session protocol (wsp) sessions |
US6421781B1 (en) * | 1998-04-30 | 2002-07-16 | Openwave Systems Inc. | Method and apparatus for maintaining security in a push server |
US6389460B1 (en) | 1998-05-13 | 2002-05-14 | Compaq Computer Corporation | Method and apparatus for efficient storage and retrieval of objects in and from an object storage device |
US6144996A (en) | 1998-05-13 | 2000-11-07 | Compaq Computer Corporation | Method and apparatus for providing a guaranteed minimum level of performance for content delivery over a network |
US6253326B1 (en) * | 1998-05-29 | 2001-06-26 | Palm, Inc. | Method and system for secure communications |
US6330561B1 (en) | 1998-06-26 | 2001-12-11 | At&T Corp. | Method and apparatus for improving end to end performance of a data network |
US6141010A (en) | 1998-07-17 | 2000-10-31 | B. E. Technology, Llc | Computer interface method and apparatus with targeted advertising |
US6112227A (en) | 1998-08-06 | 2000-08-29 | Heiner; Jeffrey Nelson | Filter-in method for reducing junk e-mail |
US6493749B2 (en) | 1998-08-17 | 2002-12-10 | International Business Machines Corporation | System and method for an administration server |
US6286043B1 (en) | 1998-08-26 | 2001-09-04 | International Business Machines Corp. | User profile management in the presence of dynamic pages using content templates |
US6564243B1 (en) | 1998-09-14 | 2003-05-13 | Adwise Ltd. | Method and system for injecting external content into computer network interactive sessions |
US6357042B2 (en) * | 1998-09-16 | 2002-03-12 | Anand Srinivasan | Method and apparatus for multiplexing separately-authored metadata for insertion into a video data stream |
US6253202B1 (en) | 1998-09-18 | 2001-06-26 | Tacit Knowledge Systems, Inc. | Method, system and apparatus for authorizing access by a first user to a knowledge profile of a second user responsive to an access request from the first user |
US6178441B1 (en) | 1998-09-21 | 2001-01-23 | International Business Machines Corporation | Method and system in a computer network for the reliable and consistent ordering of client requests |
US6223215B1 (en) | 1998-09-22 | 2001-04-24 | Sony Corporation | Tracking a user's purchases on the internet by associating the user with an inbound source and a session identifier |
US6289462B1 (en) | 1998-09-28 | 2001-09-11 | Argus Systems Group, Inc. | Trusted compartmentalized computer operating system |
US6687732B1 (en) | 1998-09-28 | 2004-02-03 | Inktomi Corporation | Adaptive traffic bypassing in an intercepting network driver |
US6606663B1 (en) | 1998-09-29 | 2003-08-12 | Openwave Systems Inc. | Method and apparatus for caching credentials in proxy servers for wireless user agents |
US6212563B1 (en) * | 1998-10-01 | 2001-04-03 | 3Com Corporation | Method and system for setting and managing externally provided internet protocol addresses using the dynamic host configuration protocol |
US6092053A (en) | 1998-10-07 | 2000-07-18 | Cybercash, Inc. | System and method for merchant invoked electronic commerce |
US6438652B1 (en) | 1998-10-09 | 2002-08-20 | International Business Machines Corporation | Load balancing cooperating cache servers by shifting forwarded request |
US20010039587A1 (en) * | 1998-10-23 | 2001-11-08 | Stephen Uhler | Method and apparatus for accessing devices on a network |
US6460141B1 (en) * | 1998-10-28 | 2002-10-01 | Rsa Security Inc. | Security and access management system for web-enabled and non-web-enabled applications and content on a computer network |
US6532493B1 (en) | 1998-10-29 | 2003-03-11 | Cisco Technology, Inc. | Methods and apparatus for redirecting network cache traffic |
US6845370B2 (en) * | 1998-11-12 | 2005-01-18 | Accenture Llp | Advanced information gathering for targeted activities |
US6487538B1 (en) * | 1998-11-16 | 2002-11-26 | Sun Microsystems, Inc. | Method and apparatus for local advertising |
US6360270B1 (en) | 1998-11-16 | 2002-03-19 | Hewlett-Packard Company | Hybrid and predictive admission control strategies for a server |
US6324585B1 (en) | 1998-11-19 | 2001-11-27 | Cisco Technology, Inc. | Method and apparatus for domain name service request resolution |
US6651095B2 (en) | 1998-12-14 | 2003-11-18 | International Business Machines Corporation | Methods, systems and computer program products for management of preferences in a heterogeneous computing environment |
US6389462B1 (en) | 1998-12-16 | 2002-05-14 | Lucent Technologies Inc. | Method and apparatus for transparently directing requests for web objects to proxy caches |
US6330588B1 (en) | 1998-12-21 | 2001-12-11 | Philips Electronics North America Corporation | Verification of software agents and agent activities |
US6718390B1 (en) | 1999-01-05 | 2004-04-06 | Cisco Technology, Inc. | Selectively forced redirection of network traffic |
US20020087559A1 (en) | 1999-01-11 | 2002-07-04 | PRATT John | Method and system for retrieving documents using hyperlinks |
US6490602B1 (en) | 1999-01-15 | 2002-12-03 | Wish-List.Com, Inc. | Method and apparatus for providing enhanced functionality to product webpages |
US6438125B1 (en) | 1999-01-22 | 2002-08-20 | Nortel Networks Limited | Method and system for redirecting web page requests on a TCP/IP network |
US6466970B1 (en) | 1999-01-27 | 2002-10-15 | International Business Machines Corporation | System and method for collecting and analyzing information about content requested in a network (World Wide Web) environment |
US6640242B1 (en) | 1999-01-29 | 2003-10-28 | Microsoft Corporation | Voice access through a data-centric network to an integrated message storage and retrieval system |
US6434608B1 (en) | 1999-02-26 | 2002-08-13 | Cisco Technology, Inc. | Methods and apparatus for caching network traffic |
US6081900A (en) * | 1999-03-16 | 2000-06-27 | Novell, Inc. | Secure intranet access |
US6212640B1 (en) * | 1999-03-25 | 2001-04-03 | Sun Microsystems, Inc. | Resources sharing on the internet via the HTTP |
US6487592B1 (en) | 1999-04-09 | 2002-11-26 | Nortel Networks Limited | Method and apparatus providing a cable modem management and provisioning system |
US6226752B1 (en) | 1999-05-11 | 2001-05-01 | Sun Microsystems, Inc. | Method and apparatus for authenticating users |
US6460081B1 (en) * | 1999-05-19 | 2002-10-01 | Qwest Communications International Inc. | System and method for controlling data access |
US7146505B1 (en) | 1999-06-01 | 2006-12-05 | America Online, Inc. | Secure data exchange between date processing systems |
US6606657B1 (en) | 1999-06-22 | 2003-08-12 | Comverse, Ltd. | System and method for processing and presenting internet usage information |
US7275086B1 (en) | 1999-07-01 | 2007-09-25 | Intellisync Corporation | System and method for embedding a context-sensitive web portal in a computer application |
US6687746B1 (en) | 1999-08-30 | 2004-02-03 | Ideaflood, Inc. | System apparatus and method for hosting and assigning domain names on a wide area network |
US7343351B1 (en) | 1999-08-31 | 2008-03-11 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
US6775687B1 (en) | 1999-10-12 | 2004-08-10 | International Business Machines Corporation | Exchanging supplemental information fields between a client and a server |
US7401115B1 (en) | 2000-10-23 | 2008-07-15 | Aol Llc | Processing selected browser requests |
US6944669B1 (en) | 1999-10-22 | 2005-09-13 | America Online, Inc. | Sharing the personal information of a network user with the resources accessed by that network user |
US7966259B1 (en) * | 1999-12-09 | 2011-06-21 | Amazon.Com, Inc. | System and methods for facilitating transactions on, and personalizing web pages of, third party web sites |
US6606643B1 (en) | 2000-01-04 | 2003-08-12 | International Business Machines Corporation | Method of automatically selecting a mirror server for web-based client-host interaction |
US7451312B2 (en) * | 2000-03-07 | 2008-11-11 | General Instrument Corporation | Authenticated dynamic address assignment |
US7130885B2 (en) | 2000-09-05 | 2006-10-31 | Zaplet, Inc. | Methods and apparatus providing electronic messages that are linked and aggregated |
US9305020B2 (en) | 2012-05-16 | 2016-04-05 | Motormouth, Llc | Media and location based social network |
-
1999
- 1999-06-01 US US09/323,415 patent/US7146505B1/en not_active Expired - Lifetime
-
2000
- 2000-06-01 AU AU53110/00A patent/AU5311000A/en not_active Abandoned
- 2000-06-01 CA CA002375443A patent/CA2375443C/en not_active Expired - Fee Related
- 2000-06-01 EP EP00938011A patent/EP1181799A2/en not_active Withdrawn
- 2000-06-01 WO PCT/US2000/015050 patent/WO2000073876A2/en active Application Filing
- 2000-06-01 JP JP2001500930A patent/JP2003501715A/en not_active Ceased
-
2006
- 2006-09-25 US US11/535,056 patent/US7895446B2/en not_active Expired - Lifetime
-
2011
- 2011-02-18 US US13/030,986 patent/US8713690B2/en not_active Expired - Lifetime
-
2012
- 2012-09-14 US US13/616,620 patent/US8751790B2/en not_active Expired - Lifetime
- 2012-09-14 US US13/616,516 patent/US8713694B2/en not_active Expired - Lifetime
- 2012-09-14 US US13/616,540 patent/US8713695B2/en not_active Expired - Lifetime
-
2013
- 2013-03-05 US US13/786,212 patent/US20130179677A1/en not_active Abandoned
- 2013-03-05 US US13/786,273 patent/US9043892B2/en not_active Expired - Lifetime
-
2014
- 2014-12-30 US US14/586,844 patent/US9363237B2/en not_active Expired - Lifetime
Also Published As
Publication number | Publication date |
---|---|
WO2000073876A3 (en) | 2001-07-05 |
US20130191905A1 (en) | 2013-07-25 |
EP1181799A2 (en) | 2002-02-27 |
US8713694B2 (en) | 2014-04-29 |
US20130073693A1 (en) | 2013-03-21 |
US7895446B2 (en) | 2011-02-22 |
US20130179677A1 (en) | 2013-07-11 |
US9043892B2 (en) | 2015-05-26 |
AU5311000A (en) | 2000-12-18 |
US20110145590A1 (en) | 2011-06-16 |
US7146505B1 (en) | 2006-12-05 |
US20130073861A1 (en) | 2013-03-21 |
JP2003501715A (en) | 2003-01-14 |
US8713695B2 (en) | 2014-04-29 |
WO2000073876A9 (en) | 2001-08-02 |
US20070124471A1 (en) | 2007-05-31 |
US8713690B2 (en) | 2014-04-29 |
WO2000073876A2 (en) | 2000-12-07 |
US9363237B2 (en) | 2016-06-07 |
US20160014086A1 (en) | 2016-01-14 |
CA2375443A1 (en) | 2000-12-07 |
US8751790B2 (en) | 2014-06-10 |
US20130073862A1 (en) | 2013-03-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2375443C (en) | Secure data exchange between data processing systems | |
US6732277B1 (en) | Method and apparatus for dynamically accessing security credentials and related information | |
EP1157344B1 (en) | Proxy server augmenting a client request with user profile data | |
US7373517B1 (en) | System and method for encrypting and decrypting files | |
JP3605501B2 (en) | Communication system, message processing method, and computer system | |
EP1278112A1 (en) | A process for providing access of a client to a content provider server under control of a resource locator server | |
US20070204156A1 (en) | Systems and methods for providing access to network resources based upon temporary keys | |
US11652633B2 (en) | System and method for securely transmitting non-PKI encrypted messages | |
EP1388060A1 (en) | Method and apparatus for serving content from a semi-trusted server | |
WO2005008950A1 (en) | Secure seed generation protocol | |
EP3334115B1 (en) | User authentication based on token | |
US20170317836A1 (en) | Service Processing Method and Apparatus | |
US20060031680A1 (en) | System and method for controlling access to a computerized entity | |
WO2017024588A1 (en) | Service processing method and apparatus | |
CN117728942A (en) | Mutual trust code generation method, equipment verification method and electronic equipment | |
CN116996287A (en) | Data interaction management method, device, terminal equipment and storage medium | |
KR20020071644A (en) | Method for authenticating user in internet and system for the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
MKLA | Lapsed |