apt/test/interactive-helper, branch 1.8.0_rc4Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.8.0_rc42019-02-10T12:16:27ZFix various typos in the documentation2019-02-10T12:16:27ZJakub Wilkjwilk@jwilk.net2019-02-10T11:51:30Zurn:sha1:9a702b150c8ddeafa8c10c9f120dafdeb08ef93bAllow to override the directory of a request in aptwebserver2018-11-25T16:22:53ZDavid Kalnischkiesdavid@kalnischkies.de2018-11-25T15:44:03Zurn:sha1:b38060dba0273f1981caba4502eb1ffc9f8fac0e
The filename can be overridden, but sometimes it is useful to do it only
for the directory-part of the filename – e.g. if you want to let a flat
archive directory (like /var/cache/apt/archives) serve a pool-based
request like /pool/a/apt_version.deb.
Gbp-Dch: Ignore
aptwebserver: Prevent XSS in debug and file listing2018-11-25T16:22:35ZDavid Kalnischkiesdavid@kalnischkies.de2018-10-10T10:38:19Zurn:sha1:85399d2b28ba0bbd3b66e1ab50fde43a9f301f68
We sometimes autogenerate HTML pages e.g. for listing files in a
directory or for various error codes. If this would be a serious
webserver this would be a security problem (althrough a bit hard to
exploit), but as it is not shipped and intended to be used by our
testcases only the world hasn't ended & we can ignore it for
changelog and fix it for brownie points.
Gbp-Dch: Ignore
aptwebserver: Guess Content-Type from filename extension2018-11-25T16:22:25ZDavid Kalnischkiesdavid@kalnischkies.de2018-09-18T14:09:03Zurn:sha1:62fd535c5f77cea773652fa2f371025c4fd1f32c
Browsing pages served via aptwebserver is working better if we tell the
browser the Content-Type which for this simple usecase we can just do by
guessing based on the file extension – and because hardcoding a list
would be boring we just reuse the mime.types data from mime-support if
available and allow it to be overridden by files and config.
Gbp-Dch: Ignore
aptwebserver: Prefetch compressors to avoid thread crashes2018-08-19T15:25:26ZDavid Kalnischkiesdavid@kalnischkies.de2018-07-09T14:12:31Zurn:sha1:d298701bd765357905705aa133c3fdb2d1a4835c
If multiple threads act on requests (like if connection comes from a
webbrowser) a thread might request the supported compressors while
another thread is still working on creating the list to be stored in the
static cache variable.
As the price to pay for atomic and co seems to high for the fringe
usecase of manual usage of aptwebserver the patch just makes a call to
generate the list while still single threaded.
Gbp-Dch: Ignore
implement Acquire::Retries support for all items2017-12-13T22:56:29ZDavid Kalnischkiesdavid@kalnischkies.de2017-10-25T23:09:48Zurn:sha1:dff555d40bb9776b5b809e06527e46b15e78736c
Moving the Retry-implementation from individual items to the worker
implementation not only gives every file retry capability instead of
just a selected few but also avoids needing to implement it in each item
(incorrectly).
remove pointless va_copy to avoid cleanup dance2017-10-05T15:30:25ZDavid Kalnischkiesdavid@kalnischkies.de2017-10-05T12:49:27Zurn:sha1:50920fca5eff021f810d5de0cc9d2fa4d6068c50
A va_copy call needs to be closed in all branches with va_end, so these
functions would need to be reworked slightly, but we don't actually need
to copy the va_list as we don't work on it, we just push it forward, so
dropping the copy and everyone is happy.
Reported-By: cppcheck
Gbp-Dch: Ignore
Use C++11 threading support instead of pthread2017-07-20T18:50:05ZJulian Andres Klodejak@debian.org2017-07-20T18:50:05Zurn:sha1:b28636e54f682dc65aef169f201a34a8e2893369
This makes the code easier to read.
Reformat and sort all includes with clang-format2017-07-12T11:57:51ZJulian Andres Klodejak@debian.org2017-07-12T11:40:41Zurn:sha1:87274d0f22e1dfd99b2e5200e2fe75c1b804eac3
This makes it easier to see which headers includes what.
The changes were done by running
git grep -l '#\s*include' \
| grep -E '.(cc|h)$' \
| xargs sed -i -E 's/(^\s*)#(\s*)include/\1#\2 include/'
To modify all include lines by adding a space, and then running
./git-clang-format.sh.
deal with 3xx httpcodes as required by HTTP/1.1 spec2017-06-26T21:31:15ZDavid Kalnischkiesdavid@kalnischkies.de2017-05-29T11:28:01Zurn:sha1:42654d08c2ca1bee18b6947a39228a35c2409deb
An unknown code should be handled the same as the x00 code of this
group, but for redirections we used to treat 300 (and a few others)
as an error while unknown codes were considered redirections.
Instead we check now explicitly for the redirection codes we support for
redirecting (and add the 308 defined in RFC 7538) to avoid future
problems if new 3xx codes are added expecting certain behaviours.
Potentially strange would have been e.g. "305 Use Proxy" sending a
Location for the proxy to use – which wouldn't have worked and resulted
in an error anyhow, but probably confused users in the process.