TRACKING WEB SERVER
First Claim
1. A tracking web server providing a tracking and forwarding function for requests to personalized Uniform Resource Locators (URL), the tracking web server comprising:
- a memory configured to store;
i) data defining a plurality of personalized URLs; and
ii) data indicating for which personalized URLs a corresponding resource request has been received;
a receiver for receiving a URL request, and for trapping the URL request before the tracking web server attempts to access a resource identified by the URL request;
an analyzer arranged to;
identify the URL request as a personalized URL request, wherein the personalized URL request includes a first resource location having a first domain name, and a contact associated with the personalized URL,update the memory to show that a request for the personalized URL has been received,wherein the analyzer formulates a new URL request based on the personalized URL, the new URL request indicating a second domain name and a second resource location,wherein the second resource location is on a web server that is physically separate from the tracking web server, and the second domain of the second resource location is different from the first domain of the first resource location; and
a re-router arranged to transmit the new URL request to the web server.
2 Assignments
0 Petitions
Accused Products
Abstract
A web server is disclosed that is configured to track requests for web pages on a third party web server. The tracking web server traps a web page request, such as a PURL (Personalised URL) for a personalised web page, before it attempts to serve the web page requested. The URL of the web page request is analysed to determine the location of the requested page on a third party server, and details of the contact with which the personalised web page is associated. Receipt of the web page request is then recorded in a memory associated with the server, and the web page request is forwarded to the third party server for processing. The redirection to the third party web server may be seamless, such that the contact requesting the page does not know of the redirection. In this way, a tracking web server is provided which can supply a personalised tracking and forwarding function.
-
Citations
33 Claims
-
1. A tracking web server providing a tracking and forwarding function for requests to personalized Uniform Resource Locators (URL), the tracking web server comprising:
-
a memory configured to store; i) data defining a plurality of personalized URLs; and ii) data indicating for which personalized URLs a corresponding resource request has been received; a receiver for receiving a URL request, and for trapping the URL request before the tracking web server attempts to access a resource identified by the URL request; an analyzer arranged to; identify the URL request as a personalized URL request, wherein the personalized URL request includes a first resource location having a first domain name, and a contact associated with the personalized URL, update the memory to show that a request for the personalized URL has been received, wherein the analyzer formulates a new URL request based on the personalized URL, the new URL request indicating a second domain name and a second resource location, wherein the second resource location is on a web server that is physically separate from the tracking web server, and the second domain of the second resource location is different from the first domain of the first resource location; and a re-router arranged to transmit the new URL request to the web server. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11)
-
-
12. A method of tracking and forwarding requests to personalized Uniform Resource Locators (URL) with a tracking web server, the method comprising:
-
storing; i) data defining a plurality of personalized URLs; and ii) data indicating for which personalized URLs a corresponding resource request has been received; receiving a URL request at the tracking web-server, and trapping the URL request before the tracking web server attempts to access a resource identified by the URL request; identifying the received URL request as a personalized URL request that includes a personalized URL indicating a first resource location having a first domain name; updating the memory to show that a request for the personalized URL has been received; formulating a new URL request based on the personalized URL, the new URL request indicating a second resource location and a second domain name, wherein the second resource location is on a web that is physically separate from the tracking web server, and wherein the second domain name of the second resource location is different from the first domain name; and transmitting the new URL request to the second resource location on the web server. - View Dependent Claims (13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A computer program product comprising a non-transitory computer readable medium on which computer code is stored, the computer code when executed by a computer causing the computer to track and forward requests to personalized Uniform Resource Locators (URL) with a tracking web server,
wherein the tracking and forwarding comprising: -
a) storing; i) data defining a plurality of personalized URLs; and ii) data indicating for which personalized URLs a corresponding resource request has been received; b) receiving a URL request at the tracking web server, and trapping the URL request before the tracking web server attempts to access a resource identified the URL request; c) identifying the received URL request as a personalized URL request that includes a personalized URL indicating a first resource location having a first domain name, and a contact associated with the personalized URL; d) updating the memory to show that a request for the personalized URL has been received; e) formulating a new URL request based on the personalized URL, the new URL request indicating a second resource location having a second domain name, wherein the second resource location is on a web server that is physically separate to the tracking web server, and wherein the second domain name of the second resource location is different from the first domain name; and f) transmitting the new URL request to the second resource location on the web server. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31, 32, 33)
-
Specification