Restore URL context for proxies

Patent metadata

Field	Value
Publication number	US-11356495-B2
Application number	US-202017084350-A
Country	US
Kind code	B2
Filing date	Oct 29, 2020
Priority date	Oct 29, 2020
Publication date	Jun 7, 2022
Grant date	Jun 7, 2022

Abstract

According to examples, an apparatus may include a processor that may identify a navigation event responsive to a URL being entered into an address bar of a web browser, the URL having a domain and a URL component, and may determine whether the web browser received an instruction to navigate to a return URL, in which the return URL includes a suffix domain for a proxy and does not include the URL component. The processor may also, based on a determination that the web browser received the instruction to navigate to the return URL, generate a modified URL by appending the suffix domain to the URL to restore context of the URL for the proxy and navigate the web browser to the modified URL.

First claim

What is claimed is:

1. An apparatus comprising:
a processor; and
a memory on which is stored machine-readable instructions that cause the processor to:
responsive to a uniform resource locator (URL) being received in an address bar of a web browser, identify a navigation event, the URL having a domain and a URL component that comprises at least one of:
a subdirectory;
a query string; and
a URL fragment part;
determine that the web browser received an instruction to navigate to a return URL that includes a suffix domain for a proxy and does not include the URL component from the URL;
generate a modified URL by appending the suffix domain to the URL to restore context of the URL for the proxy; and
navigate the web browser to the modified URL.

2. The apparatus of claim 1 , wherein the instructions cause the processor to:
determine whether the identified navigation event is a predefined type of event; and
store the URL in a data store based on the identified navigation event being the predefined type of event.

3. The apparatus of claim 2 , wherein the predefined type of event comprises of the URL being typed into the address bar, the URL being pasted into the address bar, and/or of a link being followed that causes the URL to be entered into the address bar.

4. The apparatus of claim 1 , wherein the instructions cause the processor to:
determine whether the identified navigation event is a predefined type of event; and
discard the URL based on the identified navigation event not being the predefined type of event.

5. The apparatus of claim 1 , wherein the instructions cause the processor to:
determine whether the identified navigation event is a predefined type of event; and
navigate to the return URL based on a determination that the identified navigation event is not the predefined type of event.

6. The apparatus of claim 1 , wherein the instructions cause the processor to:
determine whether the web browser navigated to a predefined identity provider; and
determine whether the web browser received the instruction to navigate to the return URL based on a determination that the web browser navigated to the predefined identity provider.

7. The apparatus of claim 6 , wherein the web browser is to navigate to the return URL based on a determination that the web browser did not navigate to the predefined identity provider.

8. The apparatus of claim 6 , wherein the instructions cause the processor to:
determine whether the web browser navigated to the predefined identity provider within a predefined number of redirects; and
determine whether the web browser received the instruction to navigate to the return URL based on a determination that the web browser navigated to the predefined identity provider within the predefined number of redirects.

9. The apparatus of claim 8 , wherein the web browser is to navigate to the return URL based on a determination that the web browser did not navigate to the predefined identity provider within the predefined number of redirects.

10. A method comprising:
determining, by a processor, that a uniform resource locator (URL) for a destination page has been received in an address bar of a web browser, the URL including a domain and a URL component that comprises at least one of:
a subdirectory;
a query string; and
a URL fragment part;

determining, by the processor, that the web browser navigated to a predefined identity provider through a proxy server;
determining, by the processor, that the web browser received an instruction to navigate to a return URL instead of the URL, wherein the return URL includes a suffix domain of the proxy server and does not include the URL component in the URL; and
inserting, by the processor, the suffix domain of the return URL into the URL to generate a modified URL; and
navigating the web browser to a web page corresponding to the URL component included in the modified URL.

11. The method of claim 10 , further comprising:
determining whether entry of the URL into the address bar is a predefined type of entry; and
storing the URL in a data store based on the entry of the URL being the predefined type of entry.

12. The method of claim 11 , wherein the predefined type of entry comprises the URL being typed into the address bar, of the URL being pasted into the address bar, and/or a link being followed that causes the URL to be entered into the address bar.

13. The method of claim 11 , further comprising:
navigating to the return URL based on a determination that the entry of the URL is not the predefined type of entry.

14. The method of claim 10 , further comprising:
determining whether the web browser navigated to the predefined identity provider within a predefined number of redirects; and
determining whether the web browser received the instruction to navigate to the return URL based on a determination that the web browser navigated to the predefined identity provider within the predefined number of redirects.

15. The method of claim 14 , further comprising:
navigating to the return URL based on a determination that the web browser did not navigate to the predefined identity provider within the predefined number of redirects.

16. The method of claim 10 , wherein the return URL does not include the URL component in the URL.

17. A non-transitory computer-readable medium on which is stored computer-readable instructions that when executed by a processor, cause the processor to:
identify, responsive to a uniform resource locator (URL) being received in an address bar of a web browser, a navigation event, the URL having a domain and a URL component that comprises at least one of:
a subdirectory;
a query string; and
a URL fragment part;

determine that the web browser received an instruction to navigate to a return URL from a proxy server, wherein the return URL includes a suffix domain and does not include the URL component; and
generate a modified URL by inserting the suffix domain into the URL while maintaining the URL component; and
navigate the web browser to a web page corresponding to the URL component included in the modified URL.

18. The non-transitory computer-readable medium of claim 17 , wherein the instructions further cause the processor to:
determine whether the identified navigation event is a predefined type of event, wherein the predefined type of event comprises the URL being typed into the address bar, the URL being copied into the address bar, and/or a link being followed that causes the URL to be entered into the address bar; and
store the URL in a data store based on the identified navigation event being the predefined type of event.

19. The non-transitory computer-readable medium of claim 17 , wherein the instructions further cause the processor to:
determine whether the web browser navigated to a predefined identity provider; and
determine whether the web browser received the instruction to navigate to the return URL based on a determination that the web browser navigated to the predefined identity provider.

20. The non-transitory computer-readable medium of claim 19 , wherein the instructions further cause the processor to:
determine whether the web browser navigated to the predefined identity provider within a predefined number of redirects; and
determine whether the web browser received the instruction to navigate to the return URL based on a determination that the web browser navigated to the predefined identity provider within the predefined number of redirects

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Malik Vikas
• Mardiks Rappaport Nir
• Gadot Idan

Classifications

• H04L67/563

  Data redirection of data network streams · CPC title

• H04L2101/355

  containing special suffixes · CPC title

• G06F16/9566 Primary

  URL specific, e.g. using aliases, detecting broken or misspelled links · CPC title

• G06F16/954

  Navigation, e.g. using categorised browsing · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title