curl -N ba zai iya gaya wa proxy ya daina ajiya a buffer ba

curl -N, ko --no-buffer, yana kashe ajiyar buffer na rafin fitar curl. Zai iya taimakawa wajen bincikar jinkirin fitar ba tare da canza manufar buffer na proxy ko uwar garken ba.

curl --proxy http://proxy.example:8080 --noproxy '' --no-buffer --max-time 30 https://example.com/stream

Don kwatanta ta hanyar proxy na jama'a, zaɓi ƙarshen HTTP daga jerin proxy na HTTP. Yi amfani da ainihin URL ɗin rafin ku kuma zaɓi iyakar da ake nufi. Jerin wucewa mara komai yana riƙe wannan kwatancen a kan hanyar proxy da aka zaɓa.

Zuwa, yanke lamba da nunawa

Sabar uwar garke na iya samar da bytes a hankali, mai shiga tsakani na iya tattara su, ɗakin karatu na abokin ciniki na iya karanta dukkan jiki, kuma mai bincike na iya jinkirta nunawa. Kwatanta bytes na farko masu amfani da ci gaban da ya biyo baya a inda kuke sarrafa hanyar. Lokacin zane da jimlar lokacin uwar garken ba sa gano lokacin da jiki ya iso.

A cikin Guzzle, duba yawo da amfani da jiki daban. Matsawa yana ƙara matakin yanke lamba. Canjin lokacin da fitar da aka yanke ya bayyana ba ya tabbatar da kansa cewa proxy shine ɓangaren buffer.

Abin da mai shiga tsakani ke gani

Proxy na CONNECT mara haske ba zai iya nazarin amsoshin HTTPS na ciki kamar na HTTP na yau da kullum ba. Sabis ɗin binciken TLS da aka ba da izini yana da wani yanayin gani, don haka HTTPS shi kaɗai ba ya tabbatar da rashin bincike.

Da zarar an gano matakin jira, yi amfani da sarrafa yawo da wannan ɓangaren ke goyan bayan. Umarnin proxy na baya ba sa aiki kai tsaye ga proxy na gaba; alamar fitar curl tana canza sashinta ne kawai na hanyar.