apt/methods/http.cc, branch 1.9.4Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.9.42019-07-10T14:15:30ZFix typos reported by codespell in code comments2019-07-10T14:15:30ZDavid Kalnischkiesdavid@kalnischkies.de2019-07-10T14:15:30Zurn:sha1:5cfbc5727dba2f4662d24cf4deb7cab7cdd57c14
Also in old changelogs, but nothing really user visible
like error messages or alike so barely noteworthy.
Reported-By: codespell
Gbp-Dch: Ignore
Apply various suggestions by cppcheck2019-07-08T13:51:17ZDavid Kalnischkiesdavid@kalnischkies.de2019-07-08T13:48:59Zurn:sha1:2b734a7ec429825c7007c1093883229e069d36c7
Reported-By: cppcheck
http: Fix Host header in proxied https connections2019-06-11T15:27:34ZSimon Körnergit@lubiland.de2019-05-17T22:32:15Zurn:sha1:86d4d98060f36c7e71c34af20a1193a75496ef72
Currently CONNECT requests use the name of the proxy as Host value, instead of
the origin server's name.
According to RFC 2616 "The Host field value MUST represent the naming authority
of the origin server or gateway given by the original URL."
The current implementation causes problems with some proxy vendors. This
commit fixes this.
[jak: Adding a test case]
See merge request apt-team/apt!66
apt-pkg: URI: Add 'explicit' to single argument constructor2019-04-30T15:43:56ZJulian Andres Klodejulian.klode@canonical.com2019-04-30T10:32:54Zurn:sha1:af74a9e2d55d6a9532eb3fbb9b96c65b7ddc1e4d
This needs a fair amount of changes elsewhere in the code,
hence this is separate from the previous commits.
Allow setting Referer header for http method2018-11-25T16:22:43ZDavid Kalnischkiesdavid@kalnischkies.de2018-11-25T15:40:42Zurn:sha1:37de1902919ac27d4527edc4210f1f927ea376ef
Not needed for common interactions, but for some download-file
interactions it could be useful to set a specific referer as some
servers do not serve requested files otherwise.
Revert "http: Fix handling of server connection closure"2018-11-13T09:20:09ZJulian Andres Klodejulian.klode@canonical.com2018-11-13T09:19:58Zurn:sha1:9bb831d7d489eac732d4aaccc1a014d923e711ff
This reverts commit fb3f36593563d09a8d1727cc7c6deb0b49823ca2. It
caused downloads to hang on long-lived connections on certain
servers.
Gbp-Dch: full
http: Fix handling of server connection closure2018-11-12T10:51:56ZJulian Andres Klodejulian.klode@canonical.com2018-11-02T17:19:33Zurn:sha1:fb3f36593563d09a8d1727cc7c6deb0b49823ca2
If the server closed the connection while we're reading data, and
we end up not having any data left to write; that is, for example,
we received 0 bytes, then we did not exit before, as we only returned
success if there was data to write.
This is wrong: Obviously, if we have reached our limit, we are done
anyway. It's a bit unclear if we actually ever reached this part, but
it does make some sense wrt the bug below.
LP: #1801338
Use steady clock source for bandwidth limitation2018-05-29T11:04:59ZDavid Kalnischkiesdavid@kalnischkies.de2018-05-26T19:26:03Zurn:sha1:f6655a1138a11e80884959014939a25f23a1e308
Using the time of day for this is slightly wrong just like it is for
progress, just less visible.
Remove unused time-tracking from http method2018-05-28T15:59:38ZDavid Kalnischkiesdavid@kalnischkies.de2018-05-26T19:28:55Zurn:sha1:2fc09a90e7e62a4c3e4a67506bf90fcf4c6ccfaf
The Stats method isn't called anywhere, was partly commented out before,
but we keep updating the time for it – lets avoid this pointless busywork.
Gbp-Dch: Ignore
Lower default timeout from 120s to 30s2018-05-24T12:31:31ZJulian Andres Klodejulian.klode@canonical.com2018-05-24T12:31:31Zurn:sha1:329a4a6159f1972ff5ec7bc2db26430f26dc61f3
120s is an insanely high default time out, lower it to 30s
to make things a bit nicer.