MANAGING SEQUENCE VALUES WITH ADDED HEADERS IN COMPUTING DEVICES

• US 20150312384A1
• Filed: 06/19/2014
• Published: 10/29/2015
• Est. Priority Date: 04/25/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: SANKARAN, GANESH CHENNIMALAI
• Granted Patent: US 9,848,067 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

In one embodiment, the disclosure provides a data processing method comprising receiving, from a client computer, a first handshake message segment comprising a first client sequence value; sending to a server computer a second handshake message segment comprising a second client sequence value equal to the first client sequence value less an added data length value; receiving a third handshake message segment from the client computer and sending a fourth handshake message segment to the server computer and determining that connections to the client computer and the server computer have reached established states; receiving from the client computer a first data segment comprising a first data length value; forming a second data segment that comprises: payload data from the first data segment; added data that is equal in size to the added data length value; and a second data length value equal to a sum of the first data length value and the added data length value; sending the second data segment to the server computer; wherein the method is performed using one or more computing devices.

Claims

1. A data processing method comprising:

receiving, from a client computer, a first handshake message segment comprising a first client sequence value;

sending to a server computer a second handshake message segment comprising a second client sequence value equal to the first client sequence value less an added data length value;

receiving a third handshake message segment from the client computer and sending a fourth handshake message segment to the server computer and determining that connections to the client computer and the server computer have reached established states;

receiving from the client computer a first data segment comprising a first data length value;

forming a second data segment that comprises;

payload data from the first data segment;

added data that is equal in size to the added data length value; and

a second data length value equal to a sum of the first data length value and the added data length value;

sending the second data segment to the server computer;

wherein the method is performed using one or more computing devices.

2. The method of claim 1 comprising:

receiving from the client computer a third data segment that comprises a third client sequence value that is greater than a sum of the first data length value, the added data length value, and a third data length value;

sending the third data segment to the server computer without modifying the third client sequence value;

repeating the receiving and sending of claim 2 a plurality of times for a plurality of different data segments of the client computer.

3. The method of claim 1 wherein the first handshake message segment is a Transmission Control Protocol (TCP) synchronization (SYN) segment.

4. The method of claim 3 wherein the second handshake message segment is a TCP SYN ACK segment.

5. The method of claim 1 wherein the method is performed using a router that is located logically between the client computer and the server computer in a network topology.

6. The method of claim 1 further comprising:

receiving destination information in the first handshake message segment;

determining whether the destination information indicates a destination that is associated with a packet modification operation;

performing the other operations of claim 1 only in response to determining that the destination information indicates a destination that is associated with a packet modification operation.

7. The method of claim 6 wherein the destination information is a URL.

8. The method of claim 6 further comprising adding a dummy header to the proxied payload data segment in response to determining that the destination information is not associated with performing a packet modification operation.

9. The method of claim 6 wherein the added data is a new HTTP header.

11. The method of claim 10 comprising:

receiving from the client computer a third TCP data segment that comprises a third client TCP sequence value that is greater than a sum of the first data length value, the added data length value, and a third data length value;

sending the third TCP data segment to the server computer without modifying the third client sequence value;

repeating the receiving and sending of claim 1 a plurality of times for a plurality of different TCP data segments of the client computer.

22. The computer system of claim 17 comprising sequences of instructions which when executed cause performing:

receiving destination information in the first handshake message segment;

determining whether the destination information indicates a destination that is associated with a packet modification operation;

performing the other operations of claim 1 only in response to determining that the destination information indicates a destination that is associated with a packet modification operation.

23. The computer system of claim 22 comprising sequences of instructions which when executed cause performing wherein the destination information is a URL.

24. The computer system of claim 22 comprising sequences of instructions which when executed cause adding a dummy header to the proxied payload data segment in response to determining that the destination information is not associated with performing a packet modification operation.

25. The computer system of claim 22 wherein the added data is a new HTTP header.

10. A data processing method comprising:

receiving, from a client computer, a first TCP SYN segment comprising a first client TCP sequence number;

sending to a server computer a second TCP SYN segment comprising a second client TCP sequence number equal to the first client TCP sequence number less an added data length value;

receiving a first TCP SYN ACK data segment and sending a second TCP SYN ACK data segment and determining that connections to the client computer and the server computer have reached established states;

receiving from the client computer a first TCP data segment comprising a data length value;

forming a second TCP data segment that comprises;

payload data from the first TCP data segment;

added data that is equal in length to the added data length value; and

a second data length value equal to a sum of the first payload data length value and the added data length value;

sending the second TCP data segment to the server computer;

wherein the method is performed using one or more computing devices.

12. The method of claim 10 wherein the method is performed using a router that is located logically between the client computer and the server computer in a network topology.

13. The method of claim 10 further comprising:

receiving destination information in the first TCP SYN segment;

determining whether the destination information indicates a destination that is associated with a packet modification operation;

performing the other operations of claim 11 only in response to determining that the destination information indicates a destination that is associated with a packet modification operation.

14. The method of claim 13 wherein the destination information is a URL.

15. The method of claim 13 further comprising adding a dummy header to the second TCP data segment in response to determining that the destination information is not associated with performing a packet modification operation.

16. The method of claim 13 wherein the added data is a new HTTP header.

17. A computer system comprising:

one or more processors;

a switching system coupled to the one or more processors and configured to receive data packets on an ingress interface, to determine an egress interface on which to forward the data packets toward a destination from among a plurality of available egress interfaces, and to forward the data packets on the egress interface;

one or more non-transitory computer-readable storage media coupled to the one or more processors and storing one or more sequences of instructions which when executed using the one or more processors cause performing;

receiving, from a client computer, a first handshake message segment comprising a first client sequence value;

sending to a server computer a second handshake message segment comprising a second client sequence value equal to the first client sequence value less an added data length value;

receiving a third handshake message segment from the client computer and sending a fourth handshake message segment to the server computer and determining that connections to the client computer and the server computer have reached established states;

receiving from the client computer a first data segment comprising a first data length value;

forming a second data segment that comprises;

payload data from the first data segment;

added data that is equal in size to the added data length value; and

a second data length value equal to a sum of the first data length value and the added data length value;

sending the second data segment to the server computer.

18. The computer system of claim 17 comprising sequences of instructions which when executed cause performing:

receiving from the client computer a third data segment that comprises a third client sequence value that is greater than a sum of the first data length value, the added data length value, and a third data length value;

sending the third data segment to the server computer without modifying the third client sequence value;

repeating the receiving and sending of claim 2 a plurality of times for a plurality of different data segments of the client computer.

19. The computer system of claim 17 wherein the first handshake message segment is a Transmission Control Protocol (TCP) synchronization (SYN) segment.

20. The computer system of claim 19 wherein the second handshake message segment is a TCP SYN ACK segment.

21. The computer system of claim 17 comprising a router that is located logically between the client computer and the server computer in a network topology.