Method and system for processing HTTP requests with multiple application instances
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.
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 at a first URL (Universal Resource Locator) including a domain name part;
changing the first URL to a second URL by modifying the domain name part of the first URL to a new domain name different from the domain name part of the first URL by adding one or more randomly generated characters followed by a period to a header of the first URL when the domain name part of the first URL is identical to a domain name of the application, so as to generate a new HTTP request for accessing the instance of the application at a second URL including the new domain name part; and
sending the new HTTP request to a server of the application so as to access the instance of the application,
wherein the first URL and the second URL correspond to a same IP address because the second URL acts as a wildcard domain for the first URL.
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 when the domain name part of the first URL 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 part of the first URL is identical to the domain name of the application.
5. The method according to claim 4 , wherein when 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 part of the first URL is identical to the domain name of the application.
6. The method according to claim 4 , wherein when 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 part of the first URL is identical to the domain name of the application.
7. The method according to claim 1 wherein the one or more randomly generated characters satisfy a predetermined new domain name pattern.
8. 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.
9. The method according to claim 8 , 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 when 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.
10. 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.
11. The method according to claim 1 , wherein the application is a software-as-a-service application.
12. A computer program product for processing a hypertext transfer protocol HTTP request, the computer program product comprising a hardware computer readable storage medium having program code embodied therewith, the program code readable/executable by a computer to perform a method comprising:
receiving an original HTTP request for accessing an instance of an application at a first URL (Universal Resource Locator) including a domain name part;
changing the first URL to a second URL by modifying the domain name part of the first URL to a new domain name different from the domain name part of the first URL by adding one or more randomly generated characters followed by a period to a header of the first URL when the domain name part of the first URL is identical to a domain name of the application, so as to generate a new HTTP request for accessing the instance of the application at a second URL including the new domain name part; and
sending the new HTTP request to a server of the application so as to access the instance of the application,
wherein the first URL and the second URL correspond to a same IP address because the second URL acts as a wildcard domain for the first URL.
13. The computer program product according to claim 12 , wherein the original HTTP request is directly sent to the server of the application so as to access the instance of the application when the domain name part of the first URL is different from the domain name of the application.
14. The computer program product according to claim 12 , wherein the new HTTP request is returned to a client issuing the original HTTP request.
15. The computer program product according to claim 12 , wherein a URL of the original HTTP request is obtained and the domain name part of the obtained URL is analyzed so as to determine whether the domain name part of the first URL is identical to the domain name of the application.
16. The computer program product according to claim 15 , wherein it is determined that the domain name part of the first URL is identical to the domain name of the application when the domain name part of the obtained URL is identical to a domain name in a predefined application domain name list.
17. The computer program product according to claim 15 , wherein it is determined that the domain name part of the first URL is identical to the domain name of the application when a pattern of the domain name part of the obtained URL is different from a predetermined new domain name pattern.
18. The computer program product according to claim 12 , wherein the randomly generated characters satisfy a predetermined new domain name pattern.
19. The computer program product according to claim 12 , wherein 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 are recorded.
20. The computer program product according to claim 19 , wherein it is determined whether to maintain the currently received new domain name as valid based on the recorded last access time and the recorded time period, and when 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.
21. The computer program product according to claim 12 , 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, wherein the domain names to be accessed by different original HTTP requests are identical to the domain name of the same application.
22. A computer program product according to claim 12 , wherein the application is a software-as-a-service application.