Specifications

Path-Based Reverse Proxy
Host-Based Reverse Proxy
Tunneled Proxy
Replacement Proxy
Direct URL
Path-Based Reverse Proxy
The Path-Based Reverse Proxy (most commonly used) acts as the front end to your web servers on the Internet or intranet. The Barracuda SSL
VPN receives all the incoming web traffic from an external location and forwards it to the appropriate website host. For this proxy type to work, all
possible destinations on the specified website or application for a particular Web Forward Resource must be within a directory on the web server -
example: for Microsoft Outlook Web Access (OWA), and . /exchange /exchweb
This type of forward does not modify the data stream. The proxy works by matching unique paths in the request URI with the configured Web
Forwards. For example, if you have a website that is accessible from the URL in your network you can configure the reversehttp://intranet/blog
proxy Web Forward with a path of so that all requests to the SSL VPN server URL are proxied to the destination/blog https://sslvpn.myco.cc/blog
site.
With a Path-Based Reverse Proxy, the Barracuda SSL VPN attempts to automatically detect all the paths that the target website uses, and add
them to the Web Forward configuration when the Resource is launched. For example, when you create a Web Forward for http://sslvpn.myco.cc/b
log and this blog page also contains images from a path called /images from the root of the server, the Barracuda SSL VPN adds /blog and /imag
es to the Web Forward configuration. This allows anything in the or directory or subdirectories to work with this Web Forward. /blog /images The
following example shows the paths that the Barracuda SSL VPN added to the Web Forward http://sslvpn.myco.cc/blog which the user can
access:
https://sslvpn.example.com/blog/images/picture.jpg - The subdirectory of below is added to this Web Forward./images /blog
- https://sslvpn.example.com/blog/page2.htm page.2.htm, a child of /blog, is added to this Web Forward.
When you try to access this Web Forward and the web content attempts to bring up an HTTP request that is not at one of those locations, such
as: ,http://sslvpn.example.local/news/index.html the Barracuda SSL VPN automatically adds the path specified by that request; in this case: /new
Adding paths automatically does not work when they conflict with a path that the Barracuda SSL VPN uses to display HTTP content, such as s. /d
If parts of the web page are missing, the Barracuda SSL VPN might not have detected some of the paths . To resolve thisefault /theme /js /fs.
issue, edit the Web Forward, and manually add these extra paths.
Host-Based Reverse Proxy
A host-based reverse proxy works in a similar way to a path-based reverse proxy, but is not restricted to subdirectories. However, the host must
resolve properly via DNS. The proxy allows the web content to be located anywhere on the destination web server, including its root. This is
useful for websites and applications that specify a host header or use relative paths in the content.
The Host-Based Reverse Proxy creates a unique hostname and appends it to the subdomain of the Barracuda SSL VPN.
For example: If the Barracuda SSL VPN hostname is the URL for the host-based reverse proxy Web Forward would be sslvpn.myco.cc, https://<r
.sslvpn.myco.cc. Because a unique subdomain is created for each Web Forward configured as a Host-Based Reverse Proxy, youandom string>
must configure a DNS entry on your DNS server for each subdomain that is used to resolve to the Barracuda SSL VPN. You can identify every
To use the Path-Based Reverse Proxy, make sure that you set the option to .Always Launch Agent Yes