|Publication number||US7970874 B2|
|Application number||US 12/354,657|
|Publication date||Jun 28, 2011|
|Filing date||Jan 15, 2009|
|Priority date||May 23, 2003|
|Also published as||CA2429761A1, US7519679, US20050015512, US20090119391|
|Publication number||12354657, 354657, US 7970874 B2, US 7970874B2, US-B2-7970874, US7970874 B2, US7970874B2|
|Inventors||Christopher J. Kale, Baldev S. Soor|
|Original Assignee||International Business Machines Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (29), Non-Patent Citations (3), Referenced by (2), Classifications (11), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present application is a continuation application of pending U.S. patent application Ser. No. 10/729,295, which was filed on Dec. 5, 2003, which is assigned to the assignee of the present invention. The present application claims priority benefits to U.S. patent application Ser. No. 10/729,295. U.S. patent application Ser. No. 10/729,295 claims priority under 35 U.S.C. §119(a) to Canadian Patent Application No. 2,429,761 filed May 23, 2003.
The present invention relates generally to data processing systems, and in particular, to redirection of web page requests on the World Wide Web.
The World Wide Web, or WWW, is a hypertext information and communication system used on the worldwide network of computers commonly known as the Internet. WWW operates according to a client-server model using a HyperText Transfer Protocol (“HTTP”). HTTP provides user access to files using a standard page description language known as HyperText Markup Language (“HTML”). HTML is an application of Standard Generalized Markup Language (“SGML”), which is an international standard (ISO 8879) for text information processing. Files that are accessed using HTML may be provided in many different formats including text, graphics, images, sound, and video. HTML provides basic document formatting and allows a web developer to specify links to “web servers” and files. These links are specified using an addressing scheme commonly known as the Uniform Resource Locator (“URL”). By specifying a URL, an end-user or web server is able to access web pages formatted according to HTML from a web server connected to the WWW. Entering a URL often requires the input of a long string of characters. To assist the end-user, a bookmarking facility is typically provided in web browsers, allowing the end-user to save a URL for a web page being viewed. The end-user is then able to later access the bookmarked web page by selecting the bookmark from the web browser.
Over time, a web developer or data owner may wish to alter the organization or structure of web pages at a given web site. In the process, frequently, the address or URL of the web pages may also change. Consequently, when an end-user tries to access a web page for which the URL has changed, the end-user may receive an error message and be unable to connect to the desired web page. This often results in frustration and end-user dissatisfaction with the web site.
To address this problem, various solutions for redirecting an outdated URL request to a new URL have been proposed. For example, U.S. Pat. No. 6,338,082 discloses redirecting an end-user's web browser to a domain name registration site using the Domain Name System (“DNS”) if the specified URL does not exit. As known to those skilled in the art, the DNS is a system which translates domain names to Internet Protocol addresses. Similarly, U.S. Pat. No. 6,014,660 also refers to translation within the DNS service. However, redirection through the DNS of more than a few web pages may be cumbersome and administratively difficult to set up.
Other proposed solutions have focused on redirection on the web server itself. For example, it is known that a web server configuration file in web server software may be used to redirect a request for a web page from an old URL to a new URL. However, redirecting pages at the web server configuration level may require extensive involvement of a web server administrator, which may be inconvenient for both the web server administrator and the data owner, if they are not one and the same. In any event, if there are significant changes to a web page data structure, and many web pages must be redirected as a result, using the web server configuration file to redirect each web page may prove to be quite impractical. Also, a web server configuration file may not permit specific targeting or sufficient flexibility in mapping old URLs to new URLs as desired by the data owner.
Thus, what is needed is a solution for redirecting web page requests which overcomes at least some of the drawbacks or limitations of known solutions as presented above.
The present invention provides targeted web page redirection which may be readily customized by data owners.
In an embodiment, a web page request from an end-user's web browser is redirected to a Common Gateway Interface (“CGI”) script for handling the web page redirection. In an embodiment, the CGI script includes a routine for matching an old URL to a new URL provided in a lookup table. In an embodiment, each web page of an old URL has a corresponding new URL such that a web browser trying to access a web page using an old URL is always directed to a corresponding new web page, or to a relevant page if a corresponding new page does not exist. In another embodiment, a customized message may be associated with a match between an old URL and a new URL, and the customized message may be displayed prior to redirection.
The foregoing has outlined rather broadly the features and technical advantages of the present invention in order that the detailed description of the invention that follows may be letter understood. Additional features and advantages of the invention will be described hereinafter which form the subject of the claims of the invention.
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
In the following description, numerous specific details are set forth such as specific network configurations, etc. to provide a thorough understanding of the present invention. However, it will be obvious to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known circuits have been shown in block diagram form in order not to obscure the present invention in unnecessary detail. For the most part, details concerning timing considerations and the like have been omitted inasmuch as such details are not necessary to obtain a complete understanding of the present invention and are within the skills of persons of ordinary skill in the relevant art.
The web server 130 may include a central processing unit (“CPU”) 132 and an associated random access memory (“RAM”) 133. As shown, a process 300 may be stored in the storage unit 140, retrieved and temporarily stored in RAM 133, and executed on CPU 132. The web server 130 may include various I/O modules including a network I/O module 134, a user interface I/O module 135, and a storage I/O module 136. As shown in
Now referring to
Now referring to
“www.xyz.edu/admissions/grad/pages.html” may have been expanded to new web pages “www.xyz.edu/admissions/grad/program/arts/pages.html” and “www.xyz.edu/admissions/grad/program/science-engineering/pages.html” to provide more specific admission information by program. When the end-user 107 tries to access the old URL “www.xyz.edu/admissions/pages.html”, either by directly typing in the old URL in a web browser or selecting the old URL from a bookmark facility, the web page request may be automatically redirected, as explained in detail further below. A third column 230 of lookup table 200C includes a customized message corresponding to the redirection between an old URL and a new URL. For example, message 208A″ provides a customized message which may be provided to the end-user 107 when redirecting from old URL 208A to new URL 208A′.
Still referring to
While the illustrative lookup table 200C is shown as a flat table in
Now referring to
Method 300 starts and proceeds to block 302 at which a web page request is received from the end-user 107. The request may be in the form of a URL. For example, the end-user 107 may request access to “www.xyz.edu/programs/sciences” (block 206F). Method 300 receives the request and parses the URL to identify a suitable higher level URL, for example, the top level URL. In this example, the top level URL is “www.xyz.edu”. Method 300 then proceeds to block 304 at which, based on the top level URL “www.xyz.edu”, the request from the end-user 107 is passed to a CGI script associated with that top level URL. In an embodiment, the redirection of the URL request to the CGI script may be accomplished by using a “redirect” directive in a web server configuration file. Advantageously, this is the only redirection statement required in the web server configuration file. Thus, any URL requests having the top level URL “www.xyz.edu” may be automatically passed to the associated CGI script.
Entering the URL processing block 304, method 300 proceeds to block 312, at which the CGI script reads the specific web page request for “www.xyz.edu/programs/sciences” (block 206F). At block 312, the method 300 parses the URL to identify a specific web page, if possible.
The method 300 then proceeds to block 314, at which an error check and secure routine may be performed. If there is a security issue, such as harmful or malicious content in the parsed URL, the web page request may be stopped with an appropriate error message displayed (not shown). If the error check routine determines that the requested URL cannot be found, the “old URL” may be assigned the “value” of “requested web page not found.” Otherwise, method 300 may proceed to block 316 for mapping.
At block 316, method 300 may proceed to map the requested old URL to the new URL based on the mapping in the lookup table 200C (
Method 300 then proceeds to block 318, where method 300 may generate suitable HTML code corresponding to the mapping in block 316. Method 300 then leaves URL processing 304 and proceeds to block 306. At block 306, method 300 may output the message 206H″ and then output the new URL mapped from the end-user's original web page request. Method 300 then ends.
In one embodiment, the CGI script may output a web page corresponding to the new URL directly to the end-user's web browser, rather than pass an instruction back to the web server for further processing. In this case, it will be appreciated that the CGI script will require end-user identifying information to be passed on to it by the web server, so that the output can be directed to the end-user 107.
In another example, in the opposite case where an “old” web page is expanded into multiple web pages, the redirection should be made to the lowest level web page still relevant to the web page requested. In the illustrative example, the old web page corresponding to URL “www.xyz.edu/admissions/grad/pages.html” has been expanded to include further sub-index pages “www.xyz.edu/admissions/grad/program/arts/pages.html” and “www.xyz.edu/admissions/grad/program/science-engineering/pages.html” to provide more specific admission information by program. Referring to lookup table 200C, if the end-user 107 has requested the old URL “www.xyz.edu/admissions/grad/pages.html” (line 208A, column 210), the new URL will be “www.xyz.edu/admissions/grad/program/” (line 208A′, column 220). In this case, line 208A′ has been mapped as the “most relevant” page in the new web page data structure. When a web page data structure is changed in this manner, there may be many such instances in which only the data owner knows how the web page mapping should be made. Redirection software that relies on pattern matching, or some other non-specific redirection method, may not provide the targeted redirection desired. The data owner specified mapping provided by the lookup table 200C of the present embodiment provides accurate, targeted redirection of web page requests, which may lead to increased end-user satisfaction.
In a further example, if the end-user 107 has specified a URL which is not found, and the method 300 has assigned to the “old URL” the value of “requested web page not found”, then at block 316, this “old URL” (line 209, column 210) may be mapped to the “home page” or “www.xyz.edu” (line 209′, column 220), such that the web page request is still directed to a “relevant page”. A customized error message 209″ may be associated with this mapping, and may be presented to the user at block 306, substantially as described above.
As will be appreciated, the lookup table 200C shown in
Also, as the CGI script may be more readily accessible to the data content owner, the data content owner may provide detailed mapping from old URLs to the new URLs with minimal intervention from the web server administrator, and update the CGI script whenever required. Also, a customized message may be associated with each mapping to provide an enhanced end-user experience.
In another embodiment, as the web page redirection is handled by a customized CGI script which generates the necessary HTML code (at block 318 of
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5751956||Feb 21, 1996||May 12, 1998||Infoseek Corporation||Method and apparatus for redirection of server external hyper-link references|
|US6014660||Dec 9, 1996||Jan 11, 2000||Sun Microsystems, Inc.||Method and apparatus for client-sensitive name resolution using DNS|
|US6038598||Feb 23, 1998||Mar 14, 2000||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|
|US6189030||May 1, 1998||Feb 13, 2001||Infoseek Corporation||Method and apparatus for redirection of server external hyper-link references|
|US6195097||Jul 8, 1997||Feb 27, 2001||International Business Machines Corporation||Web-based DCE management|
|US6308205||Oct 22, 1998||Oct 23, 2001||Canon Kabushiki Kaisha||Browser-based network management allowing administrators to use web browser on user's workstation to view and update configuration of network devices|
|US6338082||Mar 15, 2000||Jan 8, 2002||Eric Schneider||Method, product, and apparatus for requesting a network resource|
|US6466966||Jun 6, 2000||Oct 15, 2002||Infoseek Corporation||Method and apparatus for redirection of server external hyper-link references|
|US6606653||Oct 7, 1999||Aug 12, 2003||International Business Machines Corporation||Updating of embedded links in World Wide Web source pages to have the new URLs of their linked target Web pages after such target Web pages have been moved|
|US6952723||Feb 2, 2000||Oct 4, 2005||Telefonaktiebolaget Lm Ericsson (Publ)||Method and system for correcting invalid hyperlink address within a public network|
|US6954799 *||Dec 28, 2000||Oct 11, 2005||Charles Schwab & Co., Inc.||Method and apparatus for integrating distributed shared services system|
|US7007080 *||Dec 22, 2000||Feb 28, 2006||Solution Inc Limited||System for reconfiguring and registering a new IP address for a computer to access a different network without user intervention|
|US7031437||Dec 29, 2000||Apr 18, 2006||Nortel Networks Limited||Method and system for providing remote access to previously transmitted enterprise messages|
|US7194552||Jul 25, 2001||Mar 20, 2007||Eric Schneider||Method, product, and apparatus for requesting a network resource|
|US7519679 *||Dec 5, 2003||Apr 14, 2009||International Business Machines Corporation||Targeted web page redirection|
|US7761500 *||Feb 29, 2000||Jul 20, 2010||Cisco Technology, Inc.||URL based communication protocol from a client computer to a network device|
|US20010044825||May 18, 2001||Nov 22, 2001||Treetop Ventures Llc||Method allowing persistent links to web-pages|
|US20010051980||May 29, 2001||Dec 13, 2001||Raciborski Nathan F.||Preloading content objects on content exchanges|
|US20020054138||Dec 4, 2000||May 9, 2002||Erik Hennum||Web-based instruction|
|US20020129092||May 8, 2001||Sep 12, 2002||Envoii||Method and apparatus for a portable information agent|
|US20020194373||Jul 5, 2002||Dec 19, 2002||Choudhry Azkar Hussain||System and method for dynamic creation and management of virtual subdomain addresses|
|US20030158953||Feb 21, 2002||Aug 21, 2003||Lal Amrish K.||Protocol to fix broken links on the world wide web|
|US20030208472||Jan 23, 2003||Nov 6, 2003||Pham Peter Manh||Method and apparatus for transparent keyword-based hyperlink|
|US20040059797 *||Sep 20, 2002||Mar 25, 2004||G-Connect Ltd.||System and method for enabling a web user to control network services|
|US20050268241||Aug 2, 2005||Dec 1, 2005||Lerner Jack L||Method and apparatus for integrating distributed shared services system|
|US20060161660 *||Jan 10, 2006||Jul 20, 2006||Sebastien Brault||Method for automatic browsing in interposition mode|
|US20080172404 *||Jan 17, 2007||Jul 17, 2008||International Business Machines Corporation||Method and apparatus for bookmarking uniform resource identifiers that are subject to redirection|
|JP2000003347A||Title not available|
|JPH11272595A||Title not available|
|1||"Patent Abstracts of Japan," Hitachi Information Systems, Ltd., Aug. 10, 1999, /PA1/result/detail/main/wAAAa10898DA.|
|2||"Research Disclosure," The International Journal for companies seeking an alternative or supplement to obtaining patents. Apr. 1999, No. 420.|
|3||"Runtime Inline Transformation of CGI Script Output," IBM Business Machines Corporation, Research Disclosure, Apr. 1999, p. 575.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8996725 *||Feb 3, 2012||Mar 31, 2015||International Business Machines Corporation||Programmatic redirect management|
|US20130124755 *||Feb 3, 2012||May 16, 2013||International Business Machines Corporation||Programmatic redirect management|
|U.S. Classification||709/221, 709/203, 709/217, 709/238, 709/242, 709/220|
|International Classification||G06F15/16, H04L12/16, G06F17/30|
|Feb 6, 2015||REMI||Maintenance fee reminder mailed|
|Jun 28, 2015||LAPS||Lapse for failure to pay maintenance fees|
|Aug 18, 2015||FP||Expired due to failure to pay maintenance fee|
Effective date: 20150628