Using Router Port Forwarding And Mod Proxy; Port Forwarding - Novell IFOLDER 3.8 - DEPLOYMENT Deployment Manual

Using Router Port Forwarding and
1 2
Mod Proxy
Your organization does not always need to expose the iFolder data servers to the Internet in order to
enable users to access information through the firewall. Instead, you can use a port forwarding
mechanism and mod proxy as a means to handle requests from external users without directly
exposing the iFolder data servers.
Section 12.1, "Port Forwarding," on page 53
Section 12.2, "Mod Proxy," on page 54
Section 12.3, "Port Forwarding and Mod Proxy," on page 55
Section 12.4, "Key Benefits," on page 55
Section 12.5, "Scalability Parameters," on page 55
Section 12.6, "Deployment Scenarios," on page 56

12.1 Port Forwarding

An Apache Web server by default uses port 80 for non-secure connections and port 443 for secure
connections. You are not required to use these ports, but certain applications might need them for
connections. In this scenario, you can use the port forwarding mechanism.
The port forwarding ability is provided by the router that handles an organization's incoming
connections. For instance, a router can be configured to route all information in port 80443 to port
443 internally, which enables users to use port 80443 for iFolder service. This helps you segregate
the information coming to ports 443 and 80443 so that application-based statistics can be developed.
The figure given below illustrates how the port forwarding mechanism can be used to forward
requests from a restricted port (port 80) to an unrestricted port (8080).

Using Router Port Forwarding and Mod Proxy

12
53