It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda CloudGen Firewall

How to Configure the HTTP Proxy to Work With OWA

  • Last updated on

The HTTP Proxy supports the option of working with Outlook Web Access (OWA) as a backend web server. For this option, the HTTP Proxy accepts HTTP/S requests from the Internet and forwards them to the OWA server. Depending on your requirements, the HTTP Proxy provides different options for communicating independently with the OWA server via HTTP or HTTPS in both directions. Therefore, when answering requests with pages that include dynamic links, special requirements must be met for the configuration to provide seamless communication using either HTTP or HTTPS between the HTTP Proxy and the OWA server.

reverse_proxy_owa.png

Before You Begin

Configure the HTTP Proxy server to operate in reverse mode.

For more information, see How to Set Up a Reverse Proxy.

Configure the HTTP Proxy to Communicate with the OWA Server

Setting up the HTTP Proxy to work with the OWA server requires you to configure special settings. Since settings on the OWA server depend heavily on special release versions from Microsoft, it is recommended to consult the manuals from Microsoft to correctly set up OWA on the server side.

  1. Go to CONFIGURATION > Configuration Tree > Box > Assigned Services > HTTP Proxy > HTTP Proxy Settings.
  2. In the left menu, select Reverse Proxy Settings.
  3. Click Lock.
  4. Specify your Reverse Proxy Settings. For more information on these settings, see the following Reverse Proxy Settings section.
  5. Click Send Changes and Activate.

Reverse Proxy Settings

The following settings cover the basic configuration settings for the HTTP Proxy server to communicate with the backend OWA server in reverse mode. For additional configuration settings, see also the Microsoft manual to adjust the OWA server to communicate with the HTTP Proxy.

OptionCommunication phases / Used protocolSetting to configureConfigure value

1: Client to HTTP Proxy
4: HTTP Proxy to Client

2: HTTP Proxy to OWA
3: OWA to HTTP Proxy



11: HTTPS2: HTTPUse TLS:Provide HTTPS for HTTP backend

4: HTTPS3: HTTPSFront End HTTPS Header:On
21: HTTPS2: HTTPSUse TLS:Yes

4: HTTPS3: HTTPSFront End HTTPS Header:On
31: HTTP/HTTPS2: HTTPUse TLS:Yes

4: HTTP/HTTPS

3: HTTP/HTTPS

Front End HTTPS Header:On / Auto



MS Authentication forward:Auto