cache-test: fix race condition

The refcounting test had a race condition. Fix it by just waiting for
the stream to be destroyed, rather than asserting it already has been.

https://bugzilla.gnome.org/show_bug.cgi?id=698305
Also copy disabled features when copying messages.

https://bugzilla.gnome.org/show_bug.cgi?id=706338
soup_cookie_new: clarify the interpretation of @domain

https://bugzilla.gnome.org/show_bug.cgi?id=691840
soup-body-output-stream: fix closing of chunked stream

When closing a chunked stream, we need to write the final 0-length
chunk. However, we can only do that if we successfully wrote the
previous chunk.

https://bugzilla.gnome.org/show_bug.cgi?id=703297
soup-filter-input-stream: fix read_until() with subclasses

If doing a read_line()/read_until() in a subclass, we need to use the
subclass's read implementation rather than just going directly to the
base stream.
chunk-io-test: new test of the chunked I/O read/write streams
server-test: split SoupServer-specific tests out of misc-test
SoupServer: add :http-aliases and :https-aliases properties

Add :http-aliases and :https-aliases properties to SoupServer, to
allow it to handle requests like:

    GET daap://host:port/path HTTP/1.1

https://bugzilla.gnome.org/show_bug.cgi?id=703694
chunk-io-test: fix a bug
timeout-test: fix on very slow machines

On slow old machines, the TLS handshake when making an https request
can take longer than 1 second, which meant that even the "fast" https
requests were hitting the 1-second timeout and failing.

Fix this by making the timeouts longer. However, we don't want to do
that unless absolutely necessary, since the test has to hit this
timeout multiple times, and the test already takes 10 seconds to run
with the 1-second timeout. So check how long it takes to make a single
https request, and only slow down the rest of the tests if it looks
like it will be needed.

Also fix an unrelated bug, where the "session did/didn't close
connection" check could fail if the same memory location got used for
the first and second sockets.

https://bugzilla.gnome.org/show_bug.cgi?id=660581
cache-test: fix some minor things pointed out by coverity
Bug 708006 - libsoup fails to close connection when message cancelled

We need to clear priv->reusable when we send a request, *even* if we're
only resending a request that was already tried once (as with NTLM
authentication). Otherwise, cancellation of the pending, restarted,
request will not properly close the connection as it should.
Bug 703186 - fallback from automatic NTLM auth not working

There were two issues. Firstly, when the automatic NTLM authentication
failed we were setting conn->state to SOUP_NTLM_FAILED. So although we
would emit the 'authenticate' signal and obtain a password, we'd never
actually *try* it. We have the SOUP_NTLM_SSO_FAILED state for this, which
makes it work.

Secondly, the resulting 'authenticate' signal we being emitted with the
'retrying' property set, even when it was the first time we actually asked
for a password. This was confusing Evolution (bug 703181 comments 1-3).

Fix the latter problem by making soup_auth_ntlm_is_connection_ready()
return TRUE when the state is SOUP_NTLM_SSO_FAILED. That makes
auth_got_headers() do the right thing, and Evolution is happy again.

With this fixed, Evolution will now automatically try to connect to an
Exchange server using automatic NTLM authentication, and will fall back
to asking for a password only if it actually needs to.
2.43.92
Initial Dutch translation
Updated Indonesian translation
2.44.0
append_form_encoded: sync urlencode with php RFC1738 implementation.

From php_url_encode:
/* Allow only alphanumeric chars and '_', '-', '.'; escape the rest */

https://bugzilla.gnome.org/show_bug.cgi?id=708621
Fix asynchronicity of soup_session_queue_message() on plain SoupSession

Messages sent via soup_session_queue_message() on a plain SoupSession
accidentally ended up using blocking I/O. Fix this (and also make
switching between sync and async ops during a streaming operation work
better).

https://bugzilla.gnome.org/show_bug.cgi?id=707711
test-utils: set GSETTINGS_BACKEND=memory

To ensure we don't get unwanted proxy settings, and so we don't get
warnings if the memory backend is the only one available.