Peter Müller 66a0f3646a use protocol defined in server-list.db for mirror communication ...

For each mirror server, a protocol can be specified in the
server-list.db database. However, it was not used for the
actual URL query to a mirror before.

This might be useful for deploy HTTPS pinning for Pakfire.
If a mirror is known to support HTTPS, all queries to it
will be made with this protocol.

This saves some overhead if HTTPS is enforced on a mirror
via 301 redirects. To enable this, the server-list.db
needs to be adjusted.

The second version of this patch only handles protocols
HTTP and HTTPS, since we do not expect anything else here
at the moment.

Partially fixes #11661.

Signed-off-by: Peter Müller <peter.mueller@link38.eu>
Cc: Michael Tremer <michael.tremer@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>

2018-03-28 16:42:21 +01:00

config

Rootfile update for curl

2018-03-28 11:22:06 +01:00

doc

Update translations

2018-01-09 14:14:37 +00:00

html

As described in bug 11257 there is a mistake in the qos templates. The sum of the guaranteed bandwidth of the classes 101 - 120 is bigger than the available bandwidth. I adjusted the guaranteed bandwidth of the classes 101 - 104 so that each of them has a

2018-03-06 15:13:16 +00:00

langs

Fix capitalisation of "Root Certificate"

2018-02-06 15:45:32 +00:00

lfs

asterisk: Ship documentation

2018-03-27 20:56:31 +01:00

src

use protocol defined in server-list.db for mirror communication

2018-03-28 16:42:21 +01:00

tools

English is the reference language

2017-11-29 12:15:41 +00:00

.gitignore

Buildsystem: generate image md5sums.

2011-01-01 11:40:19 +01:00

.mailmap

Add .mailmap.

2010-01-22 11:37:55 +01:00

make.sh

Merge branch 'openssl-11' into next

2018-02-21 12:21:10 +00:00

Description

No description provided

101 MiB

Languages

Perl 70.4%

Shell 23%

C 4%

Python 0.6%

Makefile 0.5%

Other 1.4%