Systems and methods for ETAG persistency

• US 9,866,529 B2
• Filed: 04/04/2014
• Issued: 01/09/2018
• Est. Priority Date: 04/06/2013
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Khanal, Krishna, Jagadish, Ashwin, Annamalaisami, Saravana
• Primary Examiner(s): Tran, Philip B
• Application Number:
  US14/245,514
• Publication Number:
  US 20140304325A1
• Time in Patent Office: 1,376 Days
• Field of Search: 709203, 709224
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

The systems and methods of the present solution are directed to providing Entity Tag persistency by a device intermediary to a client and a plurality of servers. An intermediary device between a client and one or more back-end servers can receive an entity requested by the client from an origin server that provides the requested content. The intermediary device can encode the back-end server information onto an ETag of the entity, cache the entity with the encoded ETag and serve the entity with the encoded ETag to the client. In this way, when the client attempts to validate the entity by sending a request including the encoded ETag to the intermediary device, the intermediary device decodes the encoded ETag to extract the identity of the backend server and sends the request to validate the entity to the identified server that originally sent the entity that included the requested content.

Claims

1. A method for providing entity tag persistency by a device intermediary to a client and a plurality of servers, comprising:

receiving, by a device intermediary to a client and a plurality of servers, a first response from a server, the first response including a first entity tag corresponding to an entity;

transmitting to the client, by the device intermediary to the client and the plurality of servers, the first response modified to replace the first entity tag with a second entity tag encoded, by the device, with information used by the device to identify the server associated with the first entity tag;

receiving, by the device intermediary to the client and the plurality of servers, a client request to check a status of the entity, the client request including the second entity tag;

determining, by the device intermediary to the client and the plurality of servers, from the second entity tag included in the client request, the server that provided the first entity tag;

transmitting to the server, by the device intermediary to the client and the plurality of servers, the client request to check the status of the entity, the client request modified to replace the second entity tag with the first entity tag; and

transmitting to the client, by the device intermediary to the client and the plurality of servers, a second response from the server to the client request to check the status of the entity.

2. The method of claim 1, further comprising generating, by the device, the second entity tag by encoding server information associated with the server from which the response including the first entity tag is received by the device.

3. The method of claim 2, wherein generating the second entity tag includes inserting a character string identifying that the second entity tag is generated by the device instead of the server.

4. The method of claim 2, wherein generating the second entity tag includes encoding a global incarnation number (GIN) that corresponds to a policy applied by the device.

5. The method of claim 1, wherein the device is part of a cluster of devices intermediary to the client and the plurality of servers, each of the devices of the cluster maintaining a single global incarnation number (GIN) that corresponds to a policy applied by one or more devices of the cluster.

6. The method of claim 1, further comprising:

determining that the second entity tag included in the client request matches an entity tag stored in a cache of the device;

responsive to determining that the second entity tag included in the client request matches the entity tag stored in the cache of the device, identifying, by the device, that the first entity tag corresponds to the second entity tag; and

modifying, by the device, the client request to replace the second entity tag with the first entity tag.

7. The method of claim 1, further comprising:

responsive to determining that the second entity tag included in the client request received from the client is not generated by the device, identifying, from the second entity tag, a server to which to transmit the client request; and

transmitting, to the identified server, by the device, the client request including the second entity tag.

8. The method of claim 1, further comprising:

receiving, from the server to which the client request is transmitted, the second response that indicates that the first entity tag included in the client request transmitted to the server matches the entity tag stored at the server; and

wherein transmitting to the client, by the device, the second response to the client request to check the status of the entity, includes transmitting, to the client, the second response indicating that the entity corresponding to the first entity tag is up to date.

9. The method of claim 1, further comprising:

responsive to receiving the client request, determining, by the device, that the server from which the response was received is unavailable;

transmitting, to a second server of the plurality of servers, the client request with the second entity tag;

receiving, from the second server, a new entity and a corresponding new first entity tag associated with the second server; and

transmitting, to the client, the new entity and a new second entity tag corresponding to the new entity.

10. The method of claim 1, wherein the second entity tag includes the first entity tag, a server identifier identifying the server that generated the first entity tag, a global incarnation number (GIN) that corresponds to a policy of the device and a constant string indicating that the second entity tag is generated by the device.

11. A system for providing entity tag persistency by a device intermediary to a client and a plurality of servers, the system comprising:

a device intermediary to a client and a plurality of servers, the device configured to receive a response from a server, a first response including a first entity tag corresponding to an entity; and

an entity tag generator configured to generate a second entity tag encoded with information used by the device to identify the server associated with the first entity tag; and

wherein the device intermediary to the client and the plurality of servers is configured to;

transmit to the client, the first response modified to replace the first entity tag with the second entity tag;

receive a client request to check a status of the entity corresponding to the first entity tag, the client request including the second entity tag;

determine, from the second entity tag included in the client request, the server that provided the first entity tag;

transmit to the server, the client request to check a status of the entity, the client request modified to replace the second entity tag with the first entity tag; and

transmit to the client, a second response from the server to the client request to check the status of the entity.

12. The system of claim 11, wherein the entity tag generator is further configured to insert into the second entity tag a character string identifying that the second entity tag is generated by the device instead of the server.

13. The system of claim 11, wherein the entity tag generator is further configured to encode in the second entity tag a global incarnation number (GIN) that corresponds to a policy applied by the device.

14. The system of claim 11, wherein the device is part of a cluster of devices intermediary to the client and the plurality of servers, each of the devices of the cluster configured to maintain a single global incarnation number (GIN) that corresponds to a policy applied by one or more devices of the cluster.

15. The system of claim 11, wherein the device is further configured to:

determine that the second entity tag included in the client request matches the entity tag stored in a cache of the device;

responsive to determining that the second entity tag included in the client request matches the entity tag stored in a cache of the device, identify the first entity tag corresponding to the second entity tag; and

modify the client request to replace the second entity tag with the first entity tag.

16. The system of claim 11, wherein the device is further configured to:

responsive to determining that the second entity tag included in the client request received from the client is not generated by the device, identify, from the second entity tag, the server to which to transmit the client request; and

transmit, to the identified server, the client request including the second entity tag.

17. The system of claim 11, wherein the device is further configured to:

receive, from the server to which the client request is transmitted, the second response that indicates that the first entity tag included in the client request transmitted to the server matches the entity tag stored at the server; and

wherein to transmit to the client, the second response to the client request to check the status of the entity, the device is configured to transmit, to the client, the second response indicating that the entity corresponding to the first entity tag is up to date.

18. The system of claim 11, wherein the device is further configured to:

responsive to receiving the client request, determine that the server from which the response was received is unavailable;

transmit, to a second server of the plurality of servers, the client request with the second entity tag;

receive, from the second server, a new entity and a corresponding new first entity tag associated with the second server; and

transmit, to the client, the new entity and a new second entity tag corresponding to the new entity.

19. The system of claim 11, wherein the second entity tag includes the first entity tag, a server identifier identifying the server that generated the first entity tag, a global incarnation number (GIN) that corresponds to a policy applied by the device and a constant string indicating that the second entity tag is generated by the device.

20. The system of claim 11, wherein the device is further configured to:

receive, from the server to which the client request is transmitted, a new entity and a corresponding new first entity tag associated with the server responsive to determining that the entity is no longer up to date;

encode, using the entity tag generator, a new second entity tag with information used by the device to identify the server associated with the new first entity tag; and

wherein to transmit, to the client, a second response from the server includes transmitting, to the client, the new entity and the encoded new second entity tag.