Header for conveying trustful client address
Described are techniques including a computer-implemented method comprising appending a HyperText Transfer Protocol (HTTP) header to a HTTP request, wherein the HTTP header includes a source Internet Protocol (IP) address of a client generating the HTTP request, a universally unique identifier (UUID) of the HTTP request, a timestamp, a lifetime, a Universal Resource Locator (URL) of the HTTP request, and a signature. The method further comprises transmitting the HTTP request with the HTTP header to a web server.
1. A method comprising:
receiving, at a web server and from a proxy server, a HyperText Transfer Protocol (HTTP) request including a HTTP header, wherein the HTTP header includes a source Internet Protocol (IP) address of a client generating the HTTP request, a universally unique identifier (UUID) of the HTTP request, a timestamp, a lifetime, a Universal Resource Locator (URL) of the HTTP request, and a hash based on the source IP address, the UUID, the timestamp, the lifetime, and the URL;
validating the UUID in response to determining that there is no UUID in a UUID cache that matches the UUID in the HTTP header;
implementing the HTTP request;
adding the UUID to the UUID cache;
invalidating, after adding the UUID to the UUID cache and before an expiration of the lifetime, a future HTTP request with a future HTTP header containing the UUID based on the UUID being stored in the UUID cache;
purging the UUID from the UUID cache upon the expiration of the lifetime; and
validating, after purging the UUID from the UUID cache after the expiration of the lifetime, a second future HTTP request with a second future HTTP header containing the UUID based on the UUID not being in the UUID cache.
2. The method of claim 1 , wherein validating the HTTP header further comprises:
validating the hash by comparing the hash in the HTTP header to a generated hash, wherein the generated hash is generated by hashing the source IP address, the UUID, the timestamp, the lifetime, and the URL using a hash function that is shared between the web server and the client.
3. The method of claim 1 , wherein validating the HTTP header further comprises:
validating the lifetime by determining whether the expiration of the lifetime is after a current time.
4. The method of claim 1 , wherein the method is performed by one or more computers according to software that is downloaded to the one or more computers from a remote data processing system.
5. The method of claim 4 , wherein the method further comprises:
metering a usage of the software; and
generating an invoice based on metering the usage.
6. A computer program product comprising one or more computer readable storage media, and program instructions collectively stored on the one or more computer readable storage media, the program instructions comprising instructions configured to cause one or more processors to perform a method comprising:
receiving, at a web server and from a proxy server, a HyperText Transfer Protocol (HTTP) request including a HTTP header, wherein the HTTP header includes a source Internet Protocol (IP) address of a client generating the HTTP request, a universally unique identifier (UUID) of the HTTP request, a timestamp, a lifetime, a Universal Resource Locator (URL) of the HTTP request, and a hash based on the source IP address, the UUID, the timestamp, the lifetime, and the URL;
validating the UUID in response to determining that there is no UUID in a UUID cache that matches the UUID in the HTTP header;
implementing the HTTP request;
adding the UUID to the UUID cache;
invalidating, after adding the UUID to the UUID cache and before an expiration of the lifetime, a future HTTP request with a future HTTP header containing the UUID based on the UUID being stored in the UUID cache;
purging the UUID from the UUID cache upon the expiration of the lifetime; and
validating, after purging the UUID from the UUID cache after the expiration of the lifetime, a second future HTTP request with a second future HTTP header containing the UUID based on the UUID not being in the UUID cache.
7. The computer program product of claim 6 , wherein validating the HTTP header further comprises:
validating the hash by comparing the hash in the HTTP header to a generated hash, wherein the generated hash is generated by hashing the source IP address, the UUID, the timestamp, the lifetime, and the URL using a hash function that is shared between the web server and the client.
8. The computer program product of claim 6 , wherein validating the HTTP header further comprises:
validating the lifetime by determining whether the expiration of the lifetime is after a current time.
9. A system comprising:
one or more processors; and
one or more computer readable storage media storing program instructions which, when executed by the one or more processors, are configured to cause the one or more processors to perform a method comprising:
receiving, at a web server and from a proxy server, a HyperText Transfer Protocol (HTTP) request including a HTTP header, wherein the HTTP header includes a source Internet Protocol (IP) address of a client generating the HTTP request, a universally unique identifier (UUID) of the HTTP request, a timestamp, a lifetime, a Universal Resource Locator (URL) of the HTTP request, and a hash based on the source IP address, the UUID, the timestamp, the lifetime, and the URL;
validating the UUID in response to determining that there is no UUID in a UUID cache that matches the UUID in the HTTP header;
implementing the HTTP request;
adding the UUID to the UUID cache;
invalidating, after adding the UUID to the UUID cache and before an expiration of the lifetime, a future HTTP request with a future HTTP header containing the UUID based on the UUID being stored in the UUID cache;
purging the UUID from the UUID cache upon the expiration of the lifetime; and
validating, after purging the UUID from the UUID cache after the expiration of the lifetime, a second future HTTP request with a second future HTTP header containing the UUID based on the UUID not being in the UUID cache.
10. The system of claim 9 , wherein validating the HTTP header further comprises:
validating the hash by comparing the hash in the HTTP header to a generated hash, wherein the generated hash is generated by hashing the source IP address, the UUID, the timestamp, the lifetime, and the URL using a hash function that is shared between the web server and the client.
11. The system of claim 9 , wherein validating the HTTP header further comprises:
validating the lifetime by determining whether the expiration of the lifetime is after a current time.