Systems and methods for caching HTTP post requests and responses

• US 9,635,121 B2
• Filed: 07/31/2013
• Issued: 04/25/2017
• Est. Priority Date: 08/06/2012
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Mathew, Suresh, Rethi, Kumar
• Primary Examiner(s): Christensen, Scott B
• Application Number:
  US13/955,175
• Publication Number:
  US 20140040415A1
• Time in Patent Office: 1,364 Days
• Field of Search: None
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/2876 Pairs of inter-processing entities at each side of the network, e.g. split proxies
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

With an idempotent POST request, the URL (and headers) cannot be used as an HTTP cache key. To cache idempotent POST requests, the POST body is digested and appended the URL with the digest and used as the cache key. Subsequent requests with the same payload will end up hitting the cache rather than the origin server. A forward cache proxy at the client end and reverse cache proxy at the server end are deployed. The client sends the request to the forward proxy that looks up the cache. If there is a cache miss, the forward cache proxy digests the body and sends only the digest to the reverse proxy. The reverse cache proxy looks up request cache to find if there is a match for the request and send that request to the server.

Claims

1. A system comprising:

a processor; and

memory coupled to the processor and storing instructions that, when executed by the processor, cause the system to;

store cache keys and responses in a proxy cache for POST requests that are determined to be idempotent to enable cache hits for subsequent matching idempotent POST requests;

receive a POST request;

generate, in response to receiving the POST request, a digest of a body of the POST request;

append a URL of the POST request with the digest;

generate a cache key using the URL with the appended digest;

determine that the POST request is non-idempotent by configuring URLs and patterns in the proxy cache; and

in response to the determination that the POST request is non-idempotent, forward the non-idempotent POST request to a server.

2. The system of claim 1, wherein the memory further stores instructions for causing the system to add one or more headers and corresponding values to the cache key.

3. The system of claim 1, wherein the memory further stores instructions for causing the system to identify a subsequent POST request according to a corresponding cache key having the same body as the POST request.

4. The system of claim 3, wherein the memory further stores instructions for causing the system to reply to the subsequent POST request using data stored in a cache proxy.

5. The system of claim 1, wherein the memory further stores instructions for causing the system to determine that the POST request is non-idempotent by adding context aware headers.

6. The system of claim 1, wherein the memory further stores instructions for causing the system to determine that the POST request is non-idempotent by basing cache logic on at least one naming convention.

7. The system of claim 1, wherein determining that the POST request is non-idempotent includes determining that the URL is in a “

DO NOT CACHE”

URL list.

8. The system of claim 1, wherein the memory further stores instructions for causing the system to forward the non-idempotent POST request to the server if a cached digest and the digest of the POST request do not match.

9. The system of claim 1, wherein the memory further stores instructions for causing the system to forward the non-idempotent POST request to the server if a cache expiry time is passed.

10. The system of claim 1, wherein the memory further stores instructions for causing the system to forward the non-idempotent POST request to the server if there is a request to revalidate the POST request.

11. The system of claim 1, wherein the system is HTTP compliant.

12. The system of claim 1, wherein the POST request is at least 10 KB.

13. The system of claim 1, wherein the memory further stores instructions for causing the system to manage communications between a forward cache proxy and a reverse cache proxy.

14. The system of claim 13, wherein the memory further stores instructions for causing the system to instruct the forward cache proxy to digest the body of the POST request and to transmit the digest to the reverse cache proxy.

15. The system of claim 14, wherein the memory further stores instructions for causing the system to instruct the reverse cache proxy to identify a stored match in a request cache based on the digest.

16. The system of claim 15, wherein the memory further stores instructions for causing the system to instruct the reverse cache proxy to send a response key to the forward cache proxy based on the stored match.

17. A method comprising:

storing cache keys and responses in a proxy cache for POST requests that are determined to be idempotent to enable cache hits for subsequent matching idempotent POST requests;

receiving a POST request by a computer system;

in response to receiving the POST request, generating, by the computer system, a digest of a body of the POST request;

appending, by the computer system, a URL of the POST request with the digest;

generating a cache key using the URL with the appended digest;

determining that the POST request is non-idempotent by configuring URLs and patterns in the proxy cache; and

in response to the determination that the POST request is non-idempotent, forwarding, by the computer system, the non-idempotent POST request to a server.

18. A non-transitory computer-readable medium storing instructions that, when executed by a computer system, cause the computer system to perform operations comprising:

storing cache keys and responses in a proxy cache for POST requests that are determined to be idempotent to enable cache hits for subsequent matching idempotent POST requests;

receiving a POST request;

in response to receiving the POST request, generating a digest of a body of the POST request;

appending a URL of the POST request with the digest;

generating a cache key using the URL with the appended digest;

determining that the POST request is non-idempotent by configuring URLs and patterns in the proxy cache; and

in response to the determination that the POST request is non-idempotent, forwarding the non-idempotent POST request to a server.