IP Library Granted Patent US 9,742,859
Granted Patent B2
US 9,742,859 · App. 15/273,534 · Granted Aug 22, 2017

Network traffic management using port number redirection

Inventor: Paul Michael Martini (San Diego, CA)
Assignee: iboss, Inc.
H04L67/2814H04L29/06H04L45/22H04L45/74H04L63/08H04L67/02H04L67/146H04L67/2842H04L67/32
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,742,859
App. No.
15/273,534
Granted
Aug 22, 2017
Kind
B2
Abstract

A first request is received from a device over a network. It is determined that the first request should be redirected, based at least in part on information included in the first request. A redirect message is sent to the device over the network. A second request is received that includes the address and the port number. Responsive to determining that the port number is on the predetermined list of port numbers, modifying the second request by removing the port number. The modified second request is sent to the address.

Claims (81)

1. A system comprising:

a client comprising a processor and memory, the client configured to perform operations comprising:

receive, from a user of the client, input indicating a universal resource locator (URL) and not indicating a port number;

responsive to receiving the input, display the URL;

responsive to receiving the input, generate a first request for a resource, the first request including a first network location identifying a location of the resource on a server, the first network location including the URL and a first port number;

transmit the first request;

receive, in response to transmitting the first request, a redirect message, the redirect message including a second network location, the second network location including the URL and a second port number;

generate, in response to receiving the redirect message, a second request including the second network location;

transmit the second request;

receive a second response containing a modified resource; and

display the modified resource with the display of the URL;

a network gateway comprising a processor and memory, the network gateway configured to perform operations comprising:

receive the first request;

determining that the URL is associated with a rule indicating proxying;

generate, in response to determining that the URL is associated with a rule indicating proxying, the redirect message; and;

transmit the redirect message;

a proxy comprising a processor and memory, the proxy configured to perform operations comprising:

receive the second request;

generate, in response receiving the second request, a third request including the first network location;

transmit the third request;

receive a first response containing the resource;

generate the modified resource based on the resource;

transmit the second response containing the modified resource;

the server configured to:

receive the third request;

transmit a first response containing the resource;

a local network hosting the client, the local network configured to:

transmit messages between the client, the network gateway, and the proxy;

a wide-area network hosting the server, the wide-area network configured to:

transmit messages between the network gateway, the proxy, and the server; and

wherein the network gateway and the proxy are on the edge of the local network and on the edge of the wide-area network.

2. The system of claim 1 , wherein:

to receive the input, the client is further configured to receive the input to a web browser application;

to display the URL, the client is further configured to display the URL in an address bar of the web browser; and

to display the modified resource with the display of the URL, the client is further configured to render the modified resource in the web browser contemporaneously with the display of the URL in the address bar of the web browser.

3. The system of claim 2 , wherein to receive the input to a web browser application, the client is configured to receive keyboard input indicating typing of the URL.

4. The system of claim 1 , wherein:

the resource comprises relative pointers; and

to display the modified resource with the display of the URL, the client is configured to complete the relative pointers into full path pointers based on the URL.

5. The system of claim 1 , wherein the wide-area network comprises the Internet.

6. The system of claim 1 , wherein:

the network gateway comprises a first computer processor and a first computer memory; and

the proxy comprises a second computer processor and a second computer memory.

7. The system of claim 1 , wherein the first request is a first Transport Layer Security (TLS) Hello message and the second request is a second TLS Hello message.

8. The system of claim 1 , wherein the first request is a first Simple Mail Transport Protocol (SMTP) message and the second request is a second SMTP message.

9. The system of claim 1 , wherein the first request is a first Hypertext Transfer Protocol (HTTP) Get message and the second request is a second HTTP Get message.

10. The system of claim 1 , wherein the first request and the second request are formatted according to a particular networking protocol; and wherein the redirect message is formatted according to the same particular networking protocol.

11. A method performed by one or more computer apparatuses computer apparatus, the method comprising:

receiving, from a user of a client, input indicating a universal resource locator (URL) and not indicating a port number;

responsive to receiving the input, displaying, by the client, the URL;

responsive to receiving the input, generating, by the client, a first request for a resource, the first request including a first network location identifying a location of the resource on a server, the first network location including the URL and a first port number;

transmitting, by the client, the first request;

receiving, by a network gateway, the first request;

determining, by the network gateway, that the URL is associated with a rule indicating proxying;

generating, by the network gateway in response to determining that the URL is associated with a rule indicating proxying, a redirect message, the redirect message including a second network location, the second network location including the URL and a second port number;

transmitting, by the network gateway, the redirect message;

receiving, by the client in response to transmitting the first request, the redirect message;

generating, by the client in response to receiving the redirect message, a second request including the second network location;

transmitting, by the client, the second request;

receiving, by the proxy, the second request;

generating, by the proxy in response receiving the second request, a third request including the first network location;

transmitting, by the proxy, the third request;

receiving, by the server, the third request;

transmitting, by the server, a first response containing the resource;

receiving, by the proxy, the first response containing the resource;

generating, by the proxy, a modified resource based on the resource;

transmitting, by the proxy, a second response containing the modified resource;

receiving, by the client, the second response containing the modified resource; and

displaying, by the client, the modified resource with the display of the URL.

12. The method of claim 11 , wherein:

receiving, from a user of a client, input indicating a universal resource locator (URL) and not indicating a port number comprises receiving the input to a web browser application;

displaying, by the client, the URL comprises displaying the URL in an address bar of the web browser; and

displaying, by the client, the modified resource with the display of the URL comprises rendering the modified resource in the web browser contemporaneously with the display of the URL in the address bar of the web browser.

13. The method of claim 12 , wherein receiving the input to a web browser application comprises receiving keyboard input indicating typing of the URL.

14. The method of claim 11 , wherein:

the resource comprises relative pointers; and

displaying, by the client, the modified resource with the display of the URL comprises completing relative pointers into full path pointers based on the URL.

15. The method of claim 11 , wherein the first request is a first Transport Layer Security (TLS) Hello message and the second request is a second TLS Hello message.

16. The method of claim 11 , wherein the first request is a first Simple Mail Transport Protocol (SMTP) message and the second request is a second SMTP message.

17. The method of claim 11 , wherein the first request is a first Hypertext Transfer Protocol (HTTP) Get message and the second request is a second HTTP Get message.

18. The method of claim 11 , wherein the first request and the second request are formatted according to a particular networking protocol; and wherein the redirect message is formatted according to the same particular networking protocol.

Assignments (6)
SUPPLEMENTAL INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 28, 2023
From: IBOSS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 066158/0266 →
INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded Dec 28, 2023
From: IBOSS, INC.
To: WILMINGTON SAVINGS FUND SOCIETY, FSB
Reel/Frame 066158/0219 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY Recorded Dec 12, 2023
From: SILICON VALLEY BANK, A DIVISION OF FIRST-CITIZENS BANK TRUST COMPANY
To: IBOSS, INC.
Reel/Frame 066140/0480 →
SECURITY INTEREST Recorded Sep 19, 2022
From: IBOSS, INC.
To: SILICON VALLEY BANK
Reel/Frame 061463/0331 →
SECURITY INTEREST Recorded Dec 16, 2020
From: IBOSS, INC.
To: SILICON VALLEY BANK
Reel/Frame 054789/0680 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 23, 2017
From: MARTINI, PAUL MICHAEL
To: IBOSS, INC.
Reel/Frame 041707/0623 →
Continuity (4)
Continuation 14987486 · Jan 4, 2016
Continuation 14709160 · May 11, 2015
Continuation 14566587 · Dec 10, 2014
Related Publication 20170013078A1 · Jan 12, 2017