Lokacin da Squid zai iya ajiye fakitin APT a ajiya
Duba jigilar HTTP, ajiyar cache, girman abu da saitunan cache-control na APT kafin ka yi tsammanin buƙatun fakiti su zama bugun Squid.
APT da aptitude na iya ɗaukar fayilolin ma'ajiya ta HTTP. Squid na iya ajiye amsar HTTP da ta cancanta a cache; ba lallai ba ne abokin ciniki ya kasance mai binciken yanar gizo.
A cikin turawa ta Squid 6 ko 7, duba waɗannan abubuwan shigar lokacin da kowane jigilar fakiti har yanzu yana isa tushen:
- Saukarwar tana amfani da HTTP, ko kuma Squid yana da damar shiga musayar HTTP ta wata hanya. Tunnel ɗin HTTPS CONNECT shi kaɗai ba ya fallasa amsar fakitin don ajiya.
- Cache ɗin yana da ajiya da ta dace da aka saita. Nasara wajen tura ba ya tabbatar da cewa akwai cache na faifai.
- Rikodin ya dace da matsakaicin girman abu na babban fayil ɗin cache da ya dace. Ƙananan metadata da babban .deb na iya samun sakamako daban-daban.
- Buƙatar da amsa suna ba da izinin ajiya da sake amfani a ƙarƙashin manufofinsu na cache-control.
APT yana bayar da Acquire::http::No-Cache, Max-Age da No-Store. No-Store na iya hana ajiye fayilolin rikodin da aka nema. No-Cache yana neman sake tabbatarwa kafin a sake amfani da amsar da aka ajiye. Bincika ingantaccen tsarin APT da kuma manufar Squid.
Kwatanta wannan cikakken URL ɗin kuma bincika sakamakon cache a cikin access.log. Daban-daban masu masaukin madubi, hanyoyin ma'ajiya da suka canza ko fakitin da aka ajiye a gida na iya nufin cewa shigarwa biyu ba sa taɓa neman abin cibiyar sadarwa ɗaya.
Madubin ma'ajiya yana kula da abin da ke cikin ma'ajiya da gangan maimakon dogaro kawai da sake amfani da cache na HTTP bisa buƙata.