[Bug 1829944] Re: magic-proxy does not send along headers for errors

Steve Langasek steve.langasek at canonical.com
Thu May 23 20:42:55 UTC 2019


Hello Robert, or anyone else affected,

Accepted livecd-rootfs into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.578.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: livecd-rootfs (Ubuntu Disco)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-disco

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1829944

Title:
  magic-proxy does not send along headers for errors

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  When there is an error with the apt proxy the headers are not returned
  which makes debugging hard.

  [Test Case]

  This was tested on xenial when the release lacked the InRelease file
  by-hash.

  This can be verified manually as follows:

  * Start the proxy via

  ./magic-proxy -t `python -c "import time; print(int(time.time() -
  300))"`

  * In an empty directory do

  mkdir -p ubuntu/dists/xenial/by-hash/SHA256
  touch ubuntu/dists/xenial/InRelease
  python3 -m http.server

  * In a separate terminal telnet to port 8080 and paste

  GET /ubuntu/dists/xenial/InRelease HTTP/1.1
  HOST: localhost:8000

  followed by an empty line. Without the patch, the response will be the
  string "No InRelease file found for given mirror, suite and
  timestamp".

  With the patch applied, the response will start with a HTTP status
  line "HTTP/1.0 404 Not Found" and a set of HTTP headers.

  [Regression Potential]

  Low.  This was tested on xenial when the release lacked the InRelease
  file by-hash.  Also, this code is not yet in use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1829944/+subscriptions



More information about the foundations-bugs mailing list