On Tuesday 15 Feb 2005 05:03, Matthew Hawkins wrote: > For a long time apt-proxy appears to have been getting quite confused > over what constitutes an up-to-date Packages file. For example, right > now for me the local apt-proxy cache shows this (for sid/main): > > -rw------- 1 aptproxy nogroup 3401444 Feb 14 07:06 Packages.gz > > The upstream mirror its connected to shows this: > > -rw-r--r-- 1 mirror mirror 3401217 Feb 14 20:10 Packages.gz > > and by HTTP instead of FTP: > Packages.gz 15-Feb-2005 06:10 3.2M GZIP compressed file > > (the time difference between FTP & HTTP being the GMT offset of my TZ)
Hmm, I don't remember seeing any difference in the time handling for http and ftp, so you could well be right. And, both the original author and myself life in Europe so the timezone difference is not that big and if there was a problem we probably wouldn't have noticed it. > What else can I do to help diagnose this problem? Could you try turning debug on and having a closer look at the logfiles generated? [1] You'll see information about the times of the files and the decisions ap makes there. There are several places I can think of where something might be going wrong: 1. the interpretation of the if-modified-since: header sent by your client 2. comparing the if-modified-since time with the time of the file in the cache 3. sending an if-modified-since header to the backend http server. It would be a big help if you could narrow it down, thanks Chris [1] add to apt-proxy.conf: debug = all:9 db:7 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
