magic-proxy does not send along headers for errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Fix Released
|
Undecided
|
Unassigned |
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(
* In an empty directory do
mkdir -p ubuntu/
touch ubuntu/
python3 -m http.server
* In a separate terminal telnet to port 8080 and paste
GET /ubuntu/
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.
Related branches
- Ubuntu Core Development Team: Pending requested
-
Diff: 24 lines (+7/-0)2 files modifieddebian/changelog (+6/-0)
magic-proxy (+1/-0)
- Ubuntu Core Development Team: Pending requested
-
Diff: 24 lines (+7/-0)2 files modifieddebian/changelog (+6/-0)
magic-proxy (+1/-0)
This bug was fixed in the package livecd-rootfs - 2.586
---------------
livecd-rootfs (2.586) eoan; urgency=medium
[ Robert C Jennings ]
* magic-proxy: Send headers on error (LP: #1829944)
-- Michael Hudson-Doyle <email address hidden> Thu, 23 May 2019 12:33:21 +1200