Uma ukhetha ngamabomu isiphathi seklayenti le-Guzzle, isiteki esisekelwe ku-cURL singasebenzisa i-SOCKS:

$stack = \GuzzleHttp\HandlerStack::create(
    new \GuzzleHttp\Handler\CurlHandler()
);

$client = new \GuzzleHttp\Client([
    'handler' => $stack,
    'proxy' => 'socks5h://proxy.example.net:1080',
]);

socks5h sicela i-proxy ixazulule igama lendawo. I-Guzzle idlulisela i-endpoint ku-libcurl, ngakho ukwakhiwa kwe-libcurl okulayishiwe kufanele kusekele leyophrothokholi. Uhlu lwe-proxy ye-SOCKS5 lunikeza abazongenela i-endpoint yomphakathi ye-proxy URL yeklayenti.

Uma uhlelo seluvele lunaso isiteki seziphathi, hlola ithuluzi lokuhamba elingaphansi kwalo ngaphambi kokulishintsha futhi ulahlekelwe i-middleware. Isiphathi esilinganiselwe kuma-HTTP stream e-PHP asikwazi ukusebenzisa i-SOCKS ngenxa nje yokuthi iklayenti lithola le nketho.

Hlola inqubo eyenza isicelo. I-CLI PHP ne-PHP-FPM zingalayisha amafayela wokuhlela nezandiso ezihlukene; ukuba khona kwe-cURL kwelinye akufakazeli ukutholakala kwayo kwelinye.

Izihloko ezihlobene