On Thursday 27 of August 2020 17:26:47 William Morder via trinity-users wrote: > On Thursday 27 August 2020 08:17:24 Slávek Banko wrote: > > On Thursday 27 of August 2020 17:13:28 Michael wrote: > > > On Thursday 27 August 2020 10:05:17 am Slávek Banko wrote: > > > > Lately, I've been seeing more often that probably due to a > > > > malfunctioning transparent proxy somewhere at the provider, I'm > > > > getting corrupted and apt lists or damaged packages. And I have to > > > > download them repeatedly and repeatedly and... For such cases, it > > > > usually helps me to set up apt to know that the broken proxy is in > > > > the way: > > > > > > > > Acquire::http::Pipeline-Depth "0"; > > > > Acquire::http::No-Cache=True; > > > > Acquire::BrokenProxy=true; > > > > > > Hi Slávek, > > > > > > For those of who don't know better, where would those commands go? > > > > > > Thanks, > > > Michael > > > > > > PS: I've had this happen (rarely) as well. > > > > This is exactly from one of my machines: > > > > # cat /etc/apt/apt.conf.d/99fixbadproxy > > Acquire::http::Pipeline-Depth "0"; > > Acquire::http::No-Cache=True; > > Acquire::BrokenProxy=true; > > > > Cheers > > noted -- I will use them where needed. > > Right now I am having better luck with downloads, having used wget to > procure the packages by alternate means, then my apt-get and dpkg > voodoo. > > I am using a direct connection at present (if I did not make that > clear). Usually I am always running over Tor, but not until I get the > packages I need. (Or are you referring to a proxy not on my end, but > somewhere else in the chain?) > > Bill > Yes, I mean the proxy "somewhere along the way". In the case of proxies, which I have under my control (ie squid), these problems do not occur there. But if the provider has implemented some "next generation firewall", there may be a lousy transparent proxy at the provider. Cheers -- Slávek
Attachment:
signature.asc
Description: This is a digitally signed message part.
