summaryrefslogtreecommitdiff
path: root/README.SrvRecords
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2018-05-05 01:37:47 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2018-05-05 09:11:42 +0200
commite85987ab2281e765a2b3e19aefe7f99f656428d8 (patch)
tree69d1d582c3695695936bbbb8503ea1ca9b6486e2 /README.SrvRecords
parentb12bdeaf8acd050c5526ecc05526db70df5fd485 (diff)
move special READMEs into doc/ and format as md
The formatting is very basic and more should probably be done, but we at least get the files out of the root directory which in case of the various READMEs was confusing salsa which one display as (central) README.
Diffstat (limited to 'README.SrvRecords')
-rw-r--r--README.SrvRecords22
1 files changed, 0 insertions, 22 deletions
diff --git a/README.SrvRecords b/README.SrvRecords
deleted file mode 100644
index a3da64519..000000000
--- a/README.SrvRecords
+++ /dev/null
@@ -1,22 +0,0 @@
-DNS SRV record support in apt
-=============================
-
-Apt supports a subset of the DNS SRV server records protocol as
-described in RFC 2782 for service discovery.
-
-Before connecting to the requested server APT will send a SRV
-record request of the form "_$protocol._tcp._$host", e.g.
-"_http._tcp.ftp.debian.org" or "_http._tcp.security.debian.org".
-
-If the server sends SRV records
-as a reply APT will use those to connect to the server(s) in
-this reply. It will honor the "priority" field in the reply.
-
-However it does not implement the "weight" algorithm as described
-in RFC 2782. It will use an equal weight for each server of the
-same priority.
-
-If connecting to a server fails APT will retry with the next one
-and remove the server from the list of valid servers for this
-session.
-