[Expired for apt-cacher-ng (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: apt-cacher-ng (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I was now unable to reproduce this myself. I've dumped that particular
mirror as while I am physically close to it it frequently gave me
trouble. I also cannot remember the details to try and reproduce it
successfully.
** Changed in: apt-cacher-ng (Ubuntu)
Status: New => Incomplete
--
Thank you for the comment, Eduard. This was not just a theoretical
case. I was bitten by this while doing normal aptitude operations. I
simply used curl hoping it would show the problem more clearly. It's
been a while, so I will need some time to remember what was going on and
to prepare
Version in jessie seems to be unaffected as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440293
Title:
acng returns incorrect information (200 instead of 404)
To manage notifications about
Ehm, sorry for fingerpointing. I need to take a break after dealing with
such unintuitive tool like curl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440293
Title:
acng returns incorrect
Sorry, I just made the same mistake as you did and forgot --fail option.
There is no guarantee about return code if --fail is missing, RTFM!
(I am keen on that fact because acng uses sometimes 404 pages to carry
relevant information for different purposes which might be confused when
someone uses
Seems to be a curl bug. See:
http_proxy="localhost:3142" strace -s 4098 curl
http://archive.ubuntu.com/dists/trusty/InRelease
...
sendto(4, "GET http://archive.ubuntu.com/dists/trusty/InRelease
HTTP/1.1\r\nHost: archive.ubuntu.com\r\nUser-Agent: curl/7.47.0\r\nAccept:
*/*\r\nProxy-Connection:
Sad to see there is no activity here despite a clear test case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440293
Title:
acng returns incorrect information (200 instead of 404)
To manage
I tested this on a Raspbian wheezy install with version 0.7.11-2 and
that version, too, is unaffected by this bug. This narrows down the
regression window to between 0.7.11-2 and 0.7.26-1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- acng returns incorrect information
+ acng returns incorrect information (200 instead of 404)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440293
Title:
acng returns
** Description changed:
$ curl http://ubuntu.uhost.hk/dists/trusty/InRelease
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title404 Not Found/title
/headbody
h1Not Found/h1
pThe requested URL /dists/trusty/InRelease was not found on this server./p
hr
FWIW, I tested this on my (unpatched) lucid box and things were returned
as expected. curl without acng would put out the 404 information in
both cases. And with acng the command line prompt would simply return
without any output at all. That's expected behaviour, I guess. It
certainly doesn't
12 matches
Mail list logo
