Sie zeigen eine alte Version dieser Seite an. Zeigen Sie die aktuelle Version an.

Unterschiede anzeigen Seitenhistorie anzeigen

« Vorherige Version anzeigen Version 20 Aktuelle »


Description:

In isolated cases it can happen, that particular web pages (or applications which use HTTP(S) for communication) cannot be invoked when using the HTTP(S)-Proxy. In such a case it is necessary to create an exception for such a web page / application, so that the traffic isn't routed via the HTTP(S)-Proxy.

This article describes the options to create a bypass for particular web pages / applications, so that they aren't filtered by the HTTP(S)-Proxy.

The URLs and IP addresses needed for Microsoft 365 (formerly Office 365) can be found on the Microsoft 365 help page.

Some applications solely use the certificate integrated in the software and ignore the imported CA from the Unified Firewall (known as "Certificate Pinning"). This procedure is used by the operating systems Android and iOS by default. As a result, using Android or iOS devices in combination with the HTTP(S) proxy can lead to communication problems. Although it is possible in principle to bypass the proxy via a desktop object (see step 2), this can quickly become very timeconsuming. LANCOM Systems therefore recommends to place end devices with ndroid or iOS in a separate network without the HTTP(S) proxy. In this case, communication can still be restricted by the Application Filter or the URL/Content Filter.


Requirements:


Procedure:

1) Entering the DNS name in the HTTP-Proxy:

When the HTTP(S) proxy whitelist is used, websites are not checked by the proxy. Howerver, all data traffic with TCP ports 80 and 443 is still transfered via the HTTP(S) proxy. If non HTTP/HTTPS data traffic is tunneled via the TCP ports 80 and 443 (e.g. remote management or VPN clients in restrictive environments), it is possible, that the HTTP(S) proxy cannot process the packets and therefore does not transmit them. Therefore such data traffic must bypass the HTTP(S) proxy via a desktop object (see step 2).

1.1) Open the configuration of the Unified Firewall in a web browser and go to the menu UTM → Proxy → HTTP Proxy Settings.

1.2) Enter the desired web page in the Whitelist and click on the "Plus" button to add it to the list.

Click on Save afterwards.

Please note, that the Whitelist doesn't evaluate the URL but simply the SAN (Subject Alternative Name) of the SSL certificate. Thus it can occur, that individual sub domains cannot be invoked.



2) Creating a separate firewall rule with the public IP address of the web server:

By creating a desktop object with a separate firewall rule data traffic can bypass the HTTP(S) proxy.

Certificate Pinning as well as other mechanisms for securing communication as HSTS (HTTP Strict Transport Security) often leads to the HTTP(S) proxy not transmitting corresponding data traffic. This applies in particular to applications, which process sensitive information, e.g. healthcare and fincancial services, but also streaming provider and messaging services. Such applications can usually only be used, if its data traffic bypasses the HTTP(S) proxy. 

2.1) Open the configuration of the Unified Firewall in a web browser and click on the button to Create a host.

Please note, that only one IP address can be entered in a host object. Thus, if several IP addresses are needed, you have to create a host/network group.

2.2) Edit the following parameters and click Create:

  • Name: Enter a meaningful name for the web page object.
  • Connected to: In the dropdown-menu select the object internet.
  • IP Adress: Enter the public IP address of the web page, for which the exception should be created.

If you have several internet connections and the web page should be reachable via all of these connections, you have to set the parameter Connected to to any. Otherwise you would have to create a host object for each internet connection.

2.3) On the desktop click on the network object, select the Connection Tool and click on the host object created in step 2.2).

2.4) From the protocol list add HTTP and HTTPS.

2.5) For the protocol HTTP click once on the green arrow under Action so it points to the right and then click on None under Options.

2.6) For the parameter NAT / Masquerading select the option left-to-right and click OK.

2.7) Repeat the steps 2.5) and 2.6) for the protocoll HTTPS.

2.8)  The connection now has to look as follows. Click on Create afterwards.

2.9) Click on Activate, so that the changes are implemented by the Unified Firewall.



3) Using the intransparent HTTP(S) proxy:

When the intransparent HTTP(S) proxy is used, the proxy information have to be entered in the application settings or in the proxy settings in the operating system of the end device. In this case, applications behave much more tolerant. However, this operating mode requires, that the application either features its own proxy settings or that it uses the proxy entered in the operating system.

The configuration of the intransparent HTP(S) proxy is described in the following Knowledge Base article:

Use the HTTP(S) proxy of a LANCOM R&S®Unified Firewall only in the browser

  • Keine Stichwörter