METHOD AND SYSTEM AND PROCESSING HTTP REQUESTS

• US 20110078278A1
• Filed: 08/26/2010
• Published: 03/31/2011
• Est. Priority Date: 08/27/2009
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cui, Jie, Xiang, Zhe, Wang, Bin, Zhang, Jian Ming
• Granted Patent: US 8,880,711 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: G06F 16/95 Retrieval from the web
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 2101/345 containing wildcard characters
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/35 involving non-standard use of addresses for implementing network functionalities, e.g. coding subscription information within the address or functional addressing, i.e. assigning an address to a function
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method and a system for processing an HTTP request. There is provided a method for processing an HTTP request, including: receiving an original HTTP request for accessing an instance of an application; modifying a domain name to be accessed; and sending the new HTTP request to a server of the application so as to access the instance of the application, wherein the domain name to be accessed by the original HTTP request and the new domain name correspond to a same IP address. This avoids various problems such as data confusion, data error, and use inconvenience in the related art occurring when a plurality of service instances of a same application run in a same hypertext transfer protocol session. A system for carrying out the above method is also provided.

Claims

1. A method for processing a hypertext transfer protocol HTTP request, the method comprising the steps of:

receiving an original HTTP request for accessing an instance of an application;

modifying a domain name to be accessed by the original HTTP request to a new domain name different from a domain name of the application if the domain name to be accessed by the original HTTP request is identical to the domain name of the application, so as to generate a new HTTP request for accessing the instance of the application; and

sending the new HTTP request to a server of the application so as to access the instance of the application;

wherein the domain name to be accessed by the original HTTP request and the new domain name correspond to a same IP address.

2. The method according to claim 1, further comprising:

directly sending the original HTTP request to the server of the application so as to access the instance of the application if the domain name to be accessed by the original HTTP request is different from the domain name of the application.

3. The method according to claim 1, further comprising:

returning the new HTTP request to a client issuing the original HTTP request.

4. The method according to claim 1, further comprising:

obtaining a URL of the original HTTP request, and analyzing the domain name part of the obtained URL so as to determine that the domain name to be accessed by the original HTTP request is identical to the domain name of the application.

5. The method according to claim 4, wherein if the domain name part of the obtained URL is identical to a domain name in a predefined application domain name list, it is determined that the domain name to be accessed by the original HTTP request is identical to the domain name of the application.

6. The method according to claim 4, wherein if a pattern of the domain name part of the obtained URL is different from a predetermined new domain name pattern, it is determined that the domain name to be accessed by the original HTTP request is identical to the domain name of the application.

7. The method according to claim 1, further comprising:

adding a randomly generated symbol in a header of a URL of the original HTTP request.

8. The method according to claim 7 wherein the randomly generated symbol satisfies the predetermined new domain name pattern.

9. The method according to claim 1, further comprising the steps of:

recording the new domain name;

recording the last time for accessing the application according to the new domain name; and

recording the time period for setting the new domain name as an invalid domain name.

10. The method according to claim 9, further comprising:

determining whether to maintain the currently received new domain name valid based on the recorded last access time and the recorded time period, where if a determining result is no, the currently received new domain name is regarded as an original domain name identical to the domain name of the application.

11. The method according to claim 1, wherein for different original HTTP requests for accessing different instances of a same application, new domain names obtained by modification are different from each other, and the domain names to be accessed by different original HTTP requests are identical to the domain name of the same application.

12. The method according to claim 1, wherein the application is a Soft-as-a-Service application.

13. A system for processing a hypertext transfer protocol HTTP request, the system comprising:

a receiving module, for receiving an original HTTP request for accessing an instance of an application;

a modifying module configured to modify a domain name to be accessed by the original HTTP request to a new domain name different from a domain name of the application if the domain name to be accessed by the original HTTP request is identical to the domain name of the application, so as to generate a new HTTP request for accessing the instance of the application; and

a sending module configured to send the new HTTP request to a server of the application so as to access the instance of the application, wherein the domain name to be accessed by the original HTTP request and the new domain name correspond to a same IP address.

14. The system according to claim 13, wherein the sending module is further configured to directly send the original HTTP request to the server of the application so as to access the instance of the application if the domain name to be accessed by the original HTTP request is different from the domain name of the application.

15. The system according to claim 13, further comprising a returning module configured to return the new HTTP request to a client issuing the original HTTP request.

16. The system according to claim 13, further comprising a determining module for obtaining a URL of the original HTTP request and for analyzing the domain name part of the obtained URL so as to determine whether the domain name to be accessed by the original HTTP request is identical to the domain name of the application.

17. The system according to claim 16, wherein the determining module is further configured to determine that the domain name to be accessed by the original HTTP request is identical to the domain name of the application if the domain name part of the obtained URL is identical to a domain name in a predefined application domain name list.

18. The system according to claim 16, wherein the determining module is further configured to determine that the domain name to be accessed by the original HTTP request is identical to the domain name of the application if a pattern of the domain name part of the obtained URL is different from a predetermined new domain name pattern.

19. The system according to claim 13, wherein the modifying module is further configured to modify the domain name to be accessed by the original HTTP request to a new name different from the domain name of the application by adding a randomly generated symbol into a header of a URL of the original HTTP request.

20. The system according to claim 19, wherein the randomly generated symbol satisfies the predetermined new domain name pattern.

21. The system according to claim 13, further comprising a recording module configured to record the new domain name, the last time for accessing the application according to the new domain name, and the time period for setting the new domain name as an invalid domain name.

22. The system according to claim 21, wherein the determining module is further configured to determine whether to maintain the currently received new domain name as valid based on the recorded last access time and the recorded time period, and if a determining result is no, the currently received new domain name is regarded as an original domain name identical to the domain name of the application.

23. The system according to claim 13, wherein the modifying module is further configured such that for different original HTTP requests for accessing different instances of a same application, new domain names obtained by modification are different from each other, wherein the domain names to be accessed by different original HTTP requests are identical to the domain name of the same application.

24. A system according to claim 13, wherein the application is a Soft-as-a-Service application.