| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Most Certificate Authorities don't support issuing X.509 certificates for onion
sites. However, it can still be useful to provide a certificate over Tor in
some circumstances, for instance to tie your alphanumeric Tor address to your
site's main identity.
Therefore, many Tor services provide self-signed certificates. This is OK,
since the onion service itself guarantees that you are connecting to the entity
you think you are.
Dino already allows self-signed certs when communicating over Tor (see
81a5505). However, the same exception does not exist yet for HTTP uploads and
downloads - causing these to fail over Tor.
Therefore, in this commit, we add the same exception for uploads/downloads, by
passing the host of the upload/download urls to the already existing invalid
certificate connection handler.
Note that this handler only allows certificates with type
TlsCertificateFlags.UNKNOWN_CA. This means the certificate of your server must
also include the onion http upload and download URLs in its certificate -
otherwise, the file transfer will fail with TlsCertificateFlags.BAD_IDENTITY.
|
|
Required since libsoup 3.4. Fixes #1395
|
|
|
|
Note: ice plugin still depends on libsoup-2.4 and one can't have both
in the same process, so this remains disabled by default
|
|
|
|
fixes #1129 #573
|
|
|
|
|
|
fixes #756
|
|
Some services use Authorization header [0] to pass upload credential
data. This avoids the token being exposed in server logs and is allowed
by XEP-0363 since version 0.5.0.
This change adds support for headers allowed in XEP-0363: Authorization,
Expires and Cookie.
[0]: https://xmpp.org/extensions/xep-0363.html#request
|
|
Status code can't be less than 200 and greater than or equal 300 at the same
time. Using || instead of && marks all uploads that do not have 2xx status code
as "failed".
|
|
|
|
|
|
|
