edgeNEXUS’ default mode is as a Reverse Proxy: meaning that it handles incoming client requests and communicates with the load balanced servers behind it on their behalf.

In reverse proxy, incoming client connections hit the jetNEXUS Load Balancer, which then opens new and separate connections to the back-end servers (aka ‘Content Servers’ or ‘Real Servers’). This means that clients never communicate directly with the back-end servers, allowing edgeNEXUS to securely publish applications via the web. In a two-legged mode, edgeNEXUS can be set up with one-leg in the DMZ and one-leg in the internal network to ensure unauthenticated connections never make it into your internal network.

By acting as a Reverse Proxy, jetNEXUS is able to intercept application traffic and offload processes from application servers in order to improve performance, carrying out tasks like SSL Offload, Compression and Caching far more efficiently than the servers themselves.

The jetNEXUS Reverse Proxy connectivity method now features a full native UDP Proxy and can also act as an IPV6 to IPV4 Gateway.

Increase Application Security with Reverse Proxy

The edgeNEXUS reverse proxy mode can work in combination with pre-authentication to prevent unauthenticated and untrusted traffic from accessing resources residing on a private, corporate network.

edgeNEXUS Load Balancer - reverse-proxy

“The level of administration, management and monitoring offered by edgeNEXUS is far superior to all the alternative solutions we considered."