Directing clients based on communication format

• US 10,263,950 B2
• Filed: 07/03/2017
• Issued: 04/16/2019
• Est. Priority Date: 07/29/2011
• Status: Active Grant

• Current Assignee: Fortinet Inc.
• Original Assignee: Fortinet Inc.
• Inventors: Lyon, Barrett Gibson
• Primary Examiner(s): Gergiso, Techane
• Application Number:
  US15/641,151
• Publication Number:
  US 20170302622A1
• Time in Patent Office: 652 Days
• CPC Class Codes: H04L 2101/686 using dual-stack hosts, e.g. in Internet protocol version 4 [IPv4]/Internet protocol version 6 [IPv6] networks
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 47/825 Involving tunnels, e.g. MPLS
• CPC Class Codes: H04L 61/251 between different IP versions
• CPC Class Codes: H04L 61/2557 Translation policies or rules
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Methods and systems for redirecting client requests are provided. According to one embodiment, a system includes a processor and a memory coupled to the processor and configured to provide the processor with instructions. A request is received from a client capable of communicating via multiple supported communication formats. The request is capable of being serviced by multiple servers each of which are configured to communicate via a different communication format. A server is selected from the multiple servers based on a traffic management policy. The traffic management policy is based on (i) different communication formats available via the multiple servers and (ii) performance expected to be provided to the client as a result of using each of the different communication formats. The client is then redirected to the selected server.

Claims

1. A method comprising:

causing client requests for content published by a content publisher and hosted by a plurality of servers, to be directed or redirected to a traffic management node by configuring a first domain name of the content publisher to point to a second domain name associated with the traffic management node via a canonical name (CNAME) record of a domain name system (DNS), wherein a first server of the plurality of servers hosts the content in a first communication format and wherein a second server of the plurality of servers hosts the content in a second communication format;

receiving, by the traffic management node, a request for the content from a client that has been directed or redirected to the traffic management node as a result of said configuring;

selecting, by the traffic management node, the first server or the second server to service the request based on (i) a traffic management policy specified by the content publisher and (ii) performance expected to be provided to the client as a result of communicating with the client via the first communication format as compared to communicating with the client via the second communication format; and

redirecting, by the traffic management node, the client to the selected server.

2. The method of claim 1, wherein the plurality of servers comprise content publisher origin servers.

3. The method of claim 1, wherein the plurality of servers are associated with a third party entity employed to serve content on behalf of the content publisher.

4. The method of claim 3, wherein the plurality of servers are associated with a content delivery network (CDN) contracted by the content publisher.

5. The method of claim 1, wherein the first communication format comprises Internet Protocol version 4 (IPv4) and the second communication format comprises Internet Protocol version 6 (IPv6).

6. The method of claim 5, further comprising determining, by the traffic management node, whether the client is IPv4 enabled, IPv6 enabled or dual stack.

7. The method of claim 6, further comprising determining, by the traffic management node, whether the received request includes a source address associated with a tunneling service.

8. The method of claim 7, wherein said selecting, by the traffic management node, the first server or the second server to service the request is based on avoiding tunneled communications between the client and the selected server.

9. The method of claim 5, wherein said selecting, by the traffic management node, the first server or the second server to service the request is based on both the client and the server being natively connected through an IPv4 network or an IPv6 network.

10. A non-transitory computer program product embodied in a computer readable storage medium of a traffic management device, and comprising computer instructions, which when executed by one or more processors of the traffic management device perform a method of redirecting client requests, the method comprising:

receiving, a request for content from a client that has been directed or redirected to the traffic management device as a result of a first domain name of a content publisher of the content being configured to point to a second domain name associated with the traffic management device via a canonical name (CNAME) record of a domain name system (DNS), wherein the content is hosted by a plurality of servers including a first server that hosts the web page content in a first communication format and a second server that hosts the web page content in a second communication format;

selecting the first server or the second server to service the request based on (i) a traffic management policy specified by the content publisher and (ii) performance expected to be provided to the client as a result of communicating with the client via the first communication format as compared to communicating with the client via the second communication format; and

redirecting the client to the selected server.

11. The non-transitory computer program product of claim 10, wherein the plurality of servers comprise content publisher origin servers.

12. The non-transitory computer program product of claim 10, wherein the plurality of servers are associated with a third party entity employed to serve content on behalf of the content publisher.

13. The non-transitory computer program product of claim 12, wherein the plurality of servers are associated with a content delivery network (CDN) contracted by the content publisher.

14. The non-transitory computer program product of claim 10, wherein the first communication format comprises Internet Protocol version 4 (IPv4) and the second communication format comprises Internet Protocol version 6 (IPv6).

15. The non-transitory computer program product of claim 14, wherein the method further comprises determining whether the client is IPv4 enabled, IPv6 enabled or dual stack.

16. The non-transitory computer program product of claim 15, wherein the method further comprises determining whether the received request includes a source address associated with a tunneling service.

17. The non-transitory computer program product of claim 16, wherein said selecting, the first server or the second server to service the request is based on avoiding tunneled communications between the client and the selected server.

18. The non-transitory computer program product of claim 14, wherein said selecting the first server or the second server to service the request is based on both the client and the server being natively connected through an IPv4 network or an IPv6 network.