Zaɓi mai sarrafa cURL na Guzzle don SOCKS proxy

Mai sarrafa da ke tallafa wa HTTP streams kawai ba zai iya samun tattaunawar SOCKS daga proxy URL ba; zaɓi hanyar jigilar da ke tallafawa a cikin ainihin yanayin PHP.

Lokacin da kake zaɓar mai sarrafa abokin ciniki na Guzzle da gangan, tarin da ya dogara da cURL na iya amfani da SOCKS:

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

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

socks5h yana roƙon proxy ɗin warware sunan wurin da za a je. Guzzle yana miƙa ƙarshen wurin zuwa libcurl, don haka sigar libcurl da aka loda dole ta tallafa wa wannan ƙa'idar. Jerin proxy na SOCKS5 yana ba da 'yan takarar ƙarshen wuri na jama'a don proxy URL na abokin ciniki.

Idan aikace-aikacen yana da tarin mai sarrafa tuni, duba hanyar jigilar da ke ƙasa kafin ka maye gurbinsa ka rasa middleware. Mai sarrafa da ke iyakance ga HTTP streams na PHP ba zai iya aiwatar da SOCKS ba kawai saboda abokin ciniki yana karɓar wannan zaɓi.

Duba tsarin da ke yin buƙatar. CLI PHP da PHP-FPM na iya loda fayilolin saituna da kari daban-daban; kasancewar cURL a ɗaya ba ya tabbatar da samuwarsa a ɗayan.

Labarai masu alaƙa