Instead of closing the connection, as that prompted the UA to furiously
retry sending the same request many times.

Because whether something is to be stored is implied by the use of the
fresh_channel::injector_or_dcache route.

It adds no value and only causes additional traffic. It is because if
the injector_or_dcache access fails, it implies that connection to the
injector failed. And if that is the case, than neither the ::proxy
mechanism will succeed in connecting to it.

Also make dedicated functions to compute names of these (and injector
and uri) swarms.

Not using optional<error_code>{}

Not based on how many the request router already attempted to start.
Because if one access is disabled, it shoulnd't delay the following
onces.

Instead of trying one route after another, start async jobs all at once,
but each next one with an increased timeout.

Previously if there was (e.g.) POST HTTP method used, these URLs would
use those routers.

Also changed the way how we force secure HTTPS over just HTTP.

Nothing done with it yet.

They already had the same value.

Mainly to replace big blocks of code in the switch statement in that
function so that they can be made non-sequential more easily.

Fewer cache control function redirections

By printing more information about what different access strategies are
doing.

Those exchanged by the CENO extension and the ouinet/client.

And use it to announce to BitTorrent's DHT

Random BitTorrent peers may want to contact us but they don't speak HTTP
and thus the coroutines remain lingering.

To hold data inserted by the user agent. Currently the values
of request header fields X-Is-Private and X-DHT-Group.

Also don't report error if it's operation_aborted

It had redundant operations and obsolete comments.