WebSocketProxy Component

Properties   Methods   Events   Configuration Settings   Errors  

The WebSocketProxy component is used to forward traffic received on a WebSocket to another destination.

Syntax

TipeWebSocketProxy

Remarks

The WebSocketProxy component provides a simple way to accept a WebSocket connection and forward the incoming data to a separate destination host.

The WebSocketProxy component is a server that accepts incoming WebSocket connections and will establish an outgoing connection to the specified forward host and forward data it receives onto the final destination. For instance, take this diagram:

Client ---WebSocket protocol---> WebSocketProxy ---plain TCP---> Forward Host

In this example the Client establishes a WebSocket connection to the WebSocketProxy component. The WebSocketProxy component then establishes a separate standard TCP connection to Forward Host. The Client can then communicate with the Forward Host and data will be passed through WebSocketProxy.

To begin using the component first specify a valid value for LocalPort. This is the port on which incoming connections will be accepted. Specify values for DefaultForwardHost and DefaultForwardPort. This is the destination to which the data will be forwarded. Note that you may override these values on a per connection basis if desired when the client connects.

To begin listening set Listening to true.

When a client connects the WebSocketOpenRequest event will fire. To accept the connection simply allow the event to complete. To reject the request set the StatusCode parameter to an HTTP error code (such as 401). You may also set the ForwardHost and ForwardPort event parameters to override the default values.

Once the connection is established all data received on the connection will automatically be forwarded to the forward host. Any data received from the forward host will be sent back to the client. The client is now able to freely communicate with the forward host.

Note: Server components are designed to process events as they occur. To ensure events are processed in a timely manner DoEvents should be called in a loop after the server is started.