** Description changed: [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. It's hard to test otherwise unless there are problems with the - archive. + 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.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829944 Title: magic-proxy does not send along headers for errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1829944/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
