QuickFIX/J SOCKS5 Proxy Settings for an Initiator

Configure a QuickFIX/J initiator’s SOCKS5 settings while retaining the counterparty’s host and port as the session destination.

A QuickFIX/J initiator can connect through SOCKS without changing the logical FIX endpoint. In the session configuration, retain the counterparty under SocketConnectHost and SocketConnectPort:

SocketConnectHost=fix.counterparty.example
SocketConnectPort=9876
ProxyType=socks
ProxyVersion=5
ProxyHost=proxy.example
ProxyPort=1080

This fragment belongs with the existing session identifiers, schedule and other connection settings. It assumes an intermediary that permits the selected destination and needs no additional login.

ProxyHost is the first network hop. SocketConnectHost is where that intermediary should connect. Putting the proxy address into both fields can ask the SOCKS server to connect back to itself.

For a proxy account, QuickFIX/J exposes ProxyUser and ProxyPassword. Those credentials are separate from FIX logon fields and from any TLS client certificate used by the session.

Use the proxy settings documented for the deployed QuickFIX/J version. An HTTPS_PROXY value is an HTTP-client convention; it does not by itself add SOCKS negotiation to a FIX socket.

Mikanda mikatakata