WWW Proxy Service
The WWW Proxy Service provides access to the Internet for client applications that use the HTTP protocol. It also has the ability to respond to server requests based on the host header tags in the client browser request. WinGate can either reject the request, serve the request just like a web server, or redirect the request to another server if required.
Service settings
|
Default value
|
Service Port
|
80
|
Bindings
|
The WWW Proxy Service will automatically bind any interfaces that have their usage marked as Internal by WinGate.
Read more about Bindings
|
Registered events
|
ClientConnect, ConnectRequest, ProxyRequest, ProxyResponse, Request, RequestComplete, ServerRequest
|
Authentication
|
The WWW Proxy Service provides three different methods of authentication when required by Policy.
-
Negotiate
Available when using either the Windows Users and Groups user database, or an Active Directory user database in WinGate.
- NTLM
- Basic (Plaintext)
Support for each method can be enabled or disabled depending on your requirements.
|
Filters
|
By default, the WWW Proxy Service will use the Web Activity filter (for tracking on web activity on the WinGate Timeline) and the HTTP Cache for WinGate.
|
WWW Proxy Service features
-
Web server
The WWW Proxy Service has the ability to answer and fulfill server requests based on the host header tags sent in the client browser request. WinGate can serve the request just like a Web server (including support for CGI such as Pearl and PHP) or it can redirect the request to another server if required.
Read more about the Web Server tab
-
HTTPS
The WWW Proxy will handle client HTTPS (HTTP over SSL) connections automatically.
WWW Proxy Service events
When you install a new WWW Proxy Service, the service will register what events may happen during its operation with the Events system in WinGate. These events are then made available to any WinGate event processor to respond to whenever the event takes place. As an example, you can use the WinGate Policy system (an event processor) to create policies based on the occurrence of these WWW Proxy events. This allows you to specify what WinGate should do (stop/allow user access, perform an action etc.) when the registered event occurs.
Read more about service events