diff options
author | David Kalnischkies <david@kalnischkies.de> | 2020-07-09 16:38:49 +0200 |
---|---|---|
committer | David Kalnischkies <david@kalnischkies.de> | 2020-12-18 19:31:19 +0100 |
commit | e6c55283d235aa9404395d30f2db891f36995c49 (patch) | |
tree | 2ab7b38e4f6e6b0d61a4431d30866d42abe2d38a /doc/examples/configure-index | |
parent | 97be873d782c5e9aaa8b4f4f4e6e18805d0fa51c (diff) |
Keep URIs encoded in the acquire system
We do not deal a lot with URIs which need encoding, but then we do it is
a pain that we store it decoded in the acquire system as it means we
have to decode and reencode URIs eventually which is potentially giving
us slightly different URIs.
We see that in our own testing framework while setting up redirects as
the config options are effectively double-encoded and decoded to pass
them around successfully as otherwise %2f and / in an URI are treated
the same.
This commit adds the infrastructure for methods to opt into getting URIs
send in encoded form (and returning them to us in encoded form, too) so
that we eventually do not have to touch the URIs which is how it should
be. This means though that we have to deal with methods who do not
support this yet (aka: all at the moment) for which we decode and encode
while communicating with them.
Diffstat (limited to 'doc/examples/configure-index')
-rw-r--r-- | doc/examples/configure-index | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/examples/configure-index b/doc/examples/configure-index index 0af923811..b73166082 100644 --- a/doc/examples/configure-index +++ b/doc/examples/configure-index @@ -223,6 +223,8 @@ Acquire Retries "<INT>"; Source-Symlinks "<BOOL>"; ForceHash "<STRING>"; // hashmethod used for expected hash: sha256, sha1 or md5sum + Send-URI-Encoded "<BOOL>"; // false does the old encode/decode dance even if we could avoid it + URIEncode "<STRING>"; // characters to encode with percent encoding AllowTLS "<BOOL>"; // whether support for tls is enabled |