URL rescue by correction of encoding errors

• US 8,307,073 B1
• Filed: 06/24/2010
• Issued: 11/06/2012
• Est. Priority Date: 06/24/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Brundage, Michael L., Williams, Sarah E.
• Primary Examiner(s): Nguyen, Quang N.
• Application Number:
  US12/822,472
• Time in Patent Office: 866 Days
• Field of Search: 709/203, 709/223, 709/224, 709/232, 715/234
• US Class Current: 709/224
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A server system is disclosed that is capable of providing responsive content to a user when a request for an invalid URL is received. In a preferred embodiment, the server system implements multiple rescue strategies for attempting to rescue the invalid URL. One such rescue strategy involves repairing the URL by correcting for encoding errors, such as errors introduced by some web clients. Another rescue strategy involves determining that the URL contains an obsolete or outdated item identifier (e.g., product identifier) that renders the URL invalid, and returning information regarding one or more related items to the user. Another rescue strategy involves mining the invalid URL for one or more text strings reflective of the type of content desired, and then using the one or more text strings to execute a keyword search to identify content to provide to the user. The various rescue strategies may be attempted in sequence according to a hierarchy.

Claims

1. A computer-implemented method for repairing URL (Uniform Resource Locator) request messages from user computing devices, the method comprising:

receiving a URL request from a user computing device, the URL request specifying a URL that includes a name of a domain followed by a character string, the character string including a first product identifier;

determining that the URL is invalid;

at least partly in response to receiving the invalid URL, processing the invalid URL into a repaired URL using one or more computing devices, the repaired URL being different from the invalid URL, the processing comprising;

identifying a non-URL escape sequence in the character string through a comparison with known escape sequences, the escape sequence corresponding to a special character;

replacing the non-URL escape sequence in the character string with the corresponding special character; and

decoding the URL a second time by replacing a URL escape sequence in the character string with a corresponding special character, wherein the URL was previously decoded a first time; and

in response to determining whether the repaired URL resolves to valid content, (1) providing the valid content associated with the repaired URL to the user computing device when the repaired URL is valid or (2) identifying, using the first product identifier extracted from the invalid URL, a substitute URL and providing content associated with the substitute URL when the repaired URL is invalid.

2. The method of claim 1, wherein the non-URL escape sequence comprises XML encoded escape sequences.

3. The method of claim 2, wherein the XML encoded escape sequences comprises “

&

amp;

” and

the corresponding escaped character comprises “

&

”

.

4. The method of claim 1, further comprising:

determining that the repaired URL is invalid; and

at least partly in response to determining the repaired URL is invalid, returning an error message to the user computing device.

5. The method of claim 4, wherein the error comprises at least one of an HTML 404 error, an HTML 410 error and an HTML 301 error.

6. The method of claim 1, wherein the processing further comprises decoding the URL at least two times.

7. The method of claim 6, wherein decoding the URL comprises replacing one or more URL escape sequences in the character string with a corresponding special character.

8. The method of claim 1, wherein the processing further comprises:

determining that the invalid URL is encoded in a non-standard character encoding; and

converting the URL from the non-standard character encoding to a URL standard encoding.

9. The method of claim 8, wherein the non-standard character encoding comprises GBK encoding.

10. The method of claim 8, wherein the URL standard character encoding comprises UTF-8 encoding.

11. The method of claim 1, further comprising sanitizing the URL before processing the URL in order to exclude at least one character from processing.

12. The method of claim 11, wherein sanitizing the URL comprises removing “

<

”

or “

>

”

characters in the URL.

13. The method of claim 11, wherein sanitizing the URL comprises replacing “

+”

with a space character.

14. The method of claim 11, wherein the at least one excluded character comprises HTML injection code.

15. The method of claim 1, wherein the escape sequence begins with an escape character followed immediately by one or more sequence characters.

16. The method of claim 1, further comprising:

extracting information from the invalid URL;

using the extracted information to execute a keyword search; and

returning results of the keyword search to the user computing device.

17. A web site, comprising:

a computing system comprising one or more computing devices, the computing system programmed to respond to a URL (Uniform Resource Locator) request from a user computing device that specifies an invalid URL, the URL request including a name of a domain and a character string, the character string including a first product identifier, the computing system configured to respond to the URL request by at least;

identifying a non-URL escape sequence in the invalid URL through a comparison with known escape sequences, the escape sequence corresponding to a special character;

repairing the URL by replacing the non-URL escape sequence in the character string with the corresponding special character; and

decoding the URL a second time by replacing a URL escape sequence in the character string with a corresponding special character, wherein the URL was previously decoded a first time; and

in response to determining whether the repaired URL resolves to valid content providing the valid content associated with the repaired URL to the user computing device when the repaired URL is valid or (2) identifying, using the first product identifier extracted from the invalid URL, a substitute URL and providing content associated with the substitute URL when the repaired URL is invalid.

18. The system of claim 17, wherein the web site responds to at least some URL requests with a 404 error.

19. The system of claim 17, wherein the web site responds to at least some URL requests with a webpage including the web site content, wherein the webpage is not a 404 error page.

20. The system of claim 17, wherein the web site content is located on a server not on the web site.

21. The system of claim 17, wherein the escape sequence begins with an escape character followed immediately by one or more sequence characters.

22. Physical computer storage that comprises a computer readable storage medium, said physical computer storage having stored thereon instructions that, when executed, direct a computing system to:

determine that a URL (Uniform Resource Locator) received from a user computing device is invalid, the URL including a name of a domain and a character string, the character string including a first product identifier;

at least partly in response to the invalid URL request, through a conversion process, converting the invalid URL into a repaired URL, the repaired URL different from the invalid URL, the conversion process comprising;

identifying a non-URL escape sequence in the character string, the escape sequence corresponding to a special character;

replacing the non-URL escape sequence in the character string with the corresponding special character; and

decoding the URL a second time by replacing a URL escape sequence in the character string with a corresponding special character, wherein the URL was previously decoded a first time; and

in response to determining whether the repaired URL resolves to valid content, (1) provide the valid content associated with the repaired URL to the user computing device when the repaired URL is valid or (2) identify, using the first product identifier extracted from the invalid URL, a substitute URL and provide content associated with the substitute URL when the repaired URL is invalid.

23. The physical computer storage of claim 22, wherein the rescue process further comprises:

determining that the invalid URL is encoded in a non-standard character encoding; and

converting the URL from the non-standard character encoding to a URL standard encoding.

24. The physical computer storage of claim 22, further comprising instructions that, when executed, direct a computing system to sanitize the URL before the conversion process by excluding some characters from the conversion process.

25. The physical computer storage of claim 22, wherein decoding the URL comprises replacing all URL escape sequences in the character string with a corresponding special character.