Umqalisi we-QuickFIX/J angaxhuma nge-SOCKS ngaphandle kokushintsha i-FIX endpoint enengqondo. Kukho ukuhlelwa kwesikhathi, gcina umunye umuntu ngaphansi kwe-SocketConnectHost ne-SocketConnectPort:

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

Le ngxenye ihamba nezihlonzi zesikhathi ezikhona, uhlelo lwezikhathi nezinye izilungiselelo zokuxhumana. Icabanga ukuthi kukhona umlamuli ovumela indawo ekhethiwe futhi ongadingi ukungena okwengeziwe.

I-ProxyHost iyisinyathelo sokuqala senethiwekhi. I-SocketConnectHost yindawo okufanele umlamuli axhumane kuyo. Ukufaka ikheli le-proxy kuzo zombili izinkambu kungacela iseva ye-SOCKS ukuthi ixhumane nayo ngokwayo.

Ku-akhawunti ye-proxy, i-QuickFIX/J inikeza i-ProxyUser ne-ProxyPassword. Lezi ziqinisekiso zihlukile kuzinkambu zokungena ze-FIX nakunoma yisiphi isitifiketi sekhlayenti se-TLS esisetshenziswa yisikhathi.

Sebenzisa izilungiselelo ze-proxy ezibhalwe phansi zenguqulo ye-QuickFIX/J esetshenzisiwe. Inani le-HTTPS_PROXY liwumkhuba wekhlayenti le-HTTP; ngokwalo alifaki ingxoxo ye-SOCKS ku-socket ye-FIX.

Izihloko ezihlobene