On Sun, Jan 13, 2008 at 07:23:47PM +0100, Robert Luberda wrote:
> 
> I think the problem is with apt-cacher:
> 
> [13]/tmp/w> 
> URL="http://localhost/apt-cacher/ftp.debian.org/debian/dists/unstable/";
> [14]/tmp/w> wget $URL/Release.gpg $URL/Release
> --19:04:31--  
> http://localhost/apt-cacher/ftp.debian.org/debian/dists/unstable//Release.gpg
>            => `Release.gpg'

Thanks. However I can't reproduce this here.
When I use these commands everything works fine for me!

> Resolving localhost... 127.0.0.1
> Connecting to localhost|127.0.0.1|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 189 [text/plain]
> 
> 100%[==========================================================>] 189         
>   --.--K/s             
> 
> 19:04:32 (11.59 MB/s) - `Release.gpg' saved [189/189]
> 
> --19:04:32--  
> http://localhost/apt-cacher/ftp.debian.org/debian/dists/unstable//Release
>            => `Release'
> Reusing existing connection to localhost:80.
> HTTP request sent, awaiting response... 200 No headers, assuming HTTP/0.9
^
I think this is the error. The request appears to be getting garbled and there
is no header coming back, or the header comes at the end(!!!) of the
content. Something strange is happening in the HTTP conversation.

Could you repeat the same commands with debug=1, and post the contents
of /var/cache/apt-cacher/error.log

Thanks.

Mark



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to