Sake tabbatar da saukewar da aka yi ta wakili da Cache-Control: no-cache

URL ɗin saukewa daidai ne, amma wakili mai rabo har yanzu yana da amsa da aka ajiye. Idan aikin yana buƙatar amsa da aka tabbatar da asali, saka wannan buƙatar a kan roƙon:

from urllib.request import ProxyHandler, Request, build_opener
import shutil

opener = build_opener(ProxyHandler({
    "https": "http://proxy.example:8080",
}))
request = Request(download_url, headers={"Cache-Control": "no-cache"})
with opener.open(request, timeout=15) as response:
    shutil.copyfileobj(response, output)

Wannan ɓangaren yana ɗauka cewa aikace-aikacen yana da kwararar fitarwa ta binary kuma yana samar da HTTPS download_url. Don gwada saukewar jama'a da aka yarda ba tare da tantancewar wakili ba, yi amfani da ɗan takarar ƙarshen HTTP daga jerin wakilan HTTP a cikin mabudin; buƙatar cache ɗin roƙon tana nan. Yana kiyaye URL ɗin asalin albarkatun yayin da yake roƙon cache ɗin da ke kan hanyar roƙon su tabbatar kafin sake amfani.

Tabbatarwa na iya sake amfani da bytes ɗin da aka ajiye

Cache mai dacewa da ya karɓi no-cache ba zai iya cika wannan roƙon daga amsa da aka ajiye ba tare da nasarar tabbatarwa da asali ba. Asalin zai iya tabbatar da cewa wakilcin da aka ajiye yana nan da inganci, don haka aikin ba ya buƙatar sake aika fayil ɗin da ba a canza ba daga asali.

max-age=0 a cikin roƙo yana bayyana iyakar shekaru. Yana da amfani lokacin da aikace-aikacen ke son amsa da ba ta wuce wannan iyaka ba, amma ba haramci ba ne kan ajiya. Amsa da aka ƙirƙira yanzu na iya cika shi.

Ƙara bazuwar sigar tambaya yana neman wani URI manufa dabam. Wannan na iya samar da wani shigarwar cache ko ma canza amsar aikace-aikacen. Yi amfani da sigar tambaya kawai lokacin da ta kasance ɓangare na ƙayyadadden mu'amalar albarkatun.

Don HTTPS CONNECT na yau da kullum, wakilin rami ba zai iya ganin wannan kanun a cikin TLS ba. Manufar na iya isa asali da cache ɗin da ke kula da musayar HTTP da aka yanke. Duba inda amsar da aka ajiye take a zahiri kafin ka danganta ta da ramin.