Artemis na iya tsallake SOCKS don loopback broker
Duba inda broker ya nufa da halin socksRemoteDNS lokacin da haɗin Artemis ya yi nasara duk da kuskuren SOCKS da aka yi da gangan.
Haɗin broker na Artemis da ya yi nasara da kuskuren kalmar sirri ta SOCKS na iya tsallake mai sarrafa proxy. Duba inda broker ya nufa, ba socksHost kawai ba.
Takardun transport sun bayyana adiresoshin broker na loopback kamar localhost da 127.0.0.1 a matsayin adiresoshin da ke tsallake saitin SOCKS. Don hanyar warwarewar gida ta al'ada, yi amfani da adireshin broker wanda ba loopback ba da aka nufa lokacin da haɗin dole ya bi ta tsakiyar. Wani alias wanda har yanzu ya warware zuwa loopback na iya ba da sakamako ɗaya.
Duba ainihin sharadi na sigar connector
Sabon tushen connector na upstream ya haɗa da keɓancewar remote-DNS bayyananne. Shardin mai sarrafa proxy shine:
socksEnabled && (socksRemoteDNS || !isTargetLocalHost())
Lokacin da socksRemoteDNS ya kunna a cikin aiwatarwa da ke ɗauke da wannan sharadi, connector yana barin inda aka nufa ba a warware ba kuma yana saka mai sarrafa SOCKS har ma don inda ya yi kama da loopback. Tare da nuna tsoho na false, gwajin adireshin gida har yanzu yana da mahimmanci.
Wannan yana canza ma'anar sunan mai masauki kamar localhost: lokacin da aka mika shi ga uwar garken SOCKS don warwarewa, yana nufin ra'ayin proxy game da inda aka nufa. Tabbatar cewa wannan shine wurin broker da aka nufa kafin zaɓar warwarewa ta nesa.
Daidaita halin da Artemis client da aka sanya. Da zarar mai sarrafa yana cikin hanyar da gaske, bambanta tabbatarwar SOCKS daga tabbatarwar broker kuma tabbatar da hanyar haɗin da aka samu maimakon ɗaukar zaman broker mai nasara a matsayin hujjar cewa an yi amfani da takardun shaidar proxy.