AX can act as a Proxy or not depending on the VIP type. Non-Proxy VIP types: TCP, UDP. Proxy VIP types: all others (HTTP, FTP, HTTPS, SSL-Proxy, etc) Note: From release 2.6, we introduced a new type "TCP-Proxy" which is a generic TCP proxy VIP type.
When the AX acts as a Proxy for a TCP application, then you have technically 2 distinct sessions: . One TCP session between Client and AX . One other TCP session between AX and the Server
And AX to reply to your question, the AX will buffer the server response fast if the client is on a slow link. How much data the AX will buffer? By default the AX will buffer up to 87380 bytes per session. But this is configurable up to 2147483647 bytes. . WebUI: "Config >> Service >> Template >> TCP Proxy" . CLI: "slb template tcp-proxy" and assign that template to your VIP-port.
Comments
Hi Jeff,
AX can act as a Proxy or not depending on the VIP type.
Non-Proxy VIP types: TCP, UDP.
Proxy VIP types: all others (HTTP, FTP, HTTPS, SSL-Proxy, etc)
Note: From release 2.6, we introduced a new type "TCP-Proxy" which is a generic TCP proxy VIP type.
When the AX acts as a Proxy for a TCP application, then you have technically 2 distinct sessions:
. One TCP session between Client and AX
. One other TCP session between AX and the Server
And AX to reply to your question, the AX will buffer the server response fast if the client is on a slow link.
How much data the AX will buffer?
By default the AX will buffer up to 87380 bytes per session.
But this is configurable up to 2147483647 bytes.
. WebUI: "Config >> Service >> Template >> TCP Proxy"
. CLI: "slb template tcp-proxy"
and assign that template to your VIP-port.
Dimitri