This article applies to:
Question:
- Can WebMarshal function as a transparent proxy?
- What ports or protocols does WebMarshal control?
Reply:
WebMarshal does not function as a network gateway or transparent proxy.
Protocols
WebMarshal is specifically designed to monitor and control Web traffic. This includes HTTP and HTTPS, as well as browser based passive FTP traffic.
- WebMarshal can often manage traffic from media applications that normally use other protocols (such as media players and Skype), because the applications fall back to HTTP when their native protocol ports are not available. For more details, see the related articles section below.
- To manage applications and protocols that do not fall back to HTTP (for instance, to allow RDP traffic on port 3389), you use a firewall or other gateway application.
WebMarshal as standalone proxy
In this recommended configuration, WebMarshal functions as an explicit proxy and listens on specific ports.
- The default ports are 8080 and 8081. You can configure ports using the Console.
To direct traffic to these ports, you set proxy configuration for each browser or other web application, on each client computer. You can automate the client configuration using autodiscovery with proxy.pac (wpad.dat), or Windows Group Policy. For more details, see the related articles section below.
- For applications that can perform proxy authentication, you can use a Windows login credential to connect through WebMarshal.
- For applications that can use a proxy but do not understand authentication, you can use WebMarshal IP authentication.
- Applications that do not have any proxy setting cannot use WebMarshal in this mode.
Client devices should connect directly to WebMarshal for HTTP and HTTPS. Client devices will not contact WebMarshal for other ports or protocols.