[Privoxy-commits] [privoxy] 26/26: Regenerate config file

[User Git]

This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch master
in repository privoxy.

commit 08593d415b661a676ce95c05934f8929f426e957
Author: Fabian Keil <fk at fabiankeil.de>
AuthorDate: Sat Oct 10 08:28:22 2026 +0200

    Regenerate config file
    
    ... with the recently added connect-attempt-delay section.
---
 config | 60 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)

diff --git a/config b/config
index 034a4cc6..a90ff280 100644
--- a/config
+++ b/config
@@ -2444,6 +2444,66 @@ socket-timeout 300
 #            receive-buffer-size 32768
 #
 #
+#  6.20. connect-attempt-delay
+#  ============================
+#
+#  Specifies:
+#
+#      Number of milliseconds to wait before starting a connection
+#      attempt to the next address of a host while previous attempts
+#      are still pending.
+#
+#  Type of value:
+#
+#      Time in milliseconds.
+#
+#  Default value:
+#
+#      250
+#
+#  Effect if unset:
+#
+#      A default value of 250 milliseconds is used.
+#
+#  Notes:
+#
+#      If a host resolves to multiple addresses, Privoxy tries to
+#      connect to them following the "Happy Eyeballs" algorithm
+#      described in RFC 8305: the addresses are sorted so that
+#      address families alternate, the first connection attempt is
+#      started right away and additional attempts are started in
+#      parallel whenever a previous attempt fails or the
+#      connect-attempt-delay expires. The first attempt to succeed
+#      wins, the other ones are aborted.
+#
+#      This limits the delay caused by unreachable addresses, for
+#      example when a host has an IPv6 address but the system only
+#      has working IPv4 connectivity, to the configured value instead
+#      of the connection timeout.
+#
+#      RFC 8305 recommends a value between 100 and 2000 milliseconds.
+#      Setting the value to 0 disables parallel connection attempts,
+#      so that the addresses are tried one after the other with the
+#      next attempt only being started after the previous one failed.
+#
+#      Note that the addresses are resolved with a single synchronous
+#      lookup, the "Resolution Delay" described in RFC 8305 doesn't
+#      apply. The first attempt is made to the first address returned
+#      by the resolver, whichever family it belongs to, followed by
+#      an address of the other family.
+#
+#      This directive has no effect if Privoxy has been compiled
+#      without getaddrinfo() support. On platforms where the
+#      connection attempts can't be made non-blocking the addresses
+#      are tried one after the other regardless of this setting.
+#
+#  Example:
+#
+#            # Give the first address a full second before trying the next one
+#            connect-attempt-delay 1000
+#
+connect-attempt-delay 250
+#
 #  7. HTTPS INSPECTION
 #  ====================
 #

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.