Artem Boldariev cff69c65b5 Fix flawed logic when detecting same listener type ... The older version of the code was reporting that listeners are going to be of the same type after reconfiguration when switching from DoT to HTTPS listener, making BIND abort its executions. That was happening due to the flaw in logic due to which the code could consider a current listener and a configuration for the new one to be of the same type (DoT) even when the new listener entry is explicitly marked as HTTP. The checks for PROXY in between the configuration were masking that behaviour, but when porting it to 9.18 (when there is no PROXY support), the behaviour was exposed. Now the code mirrors the logic in 'interface_setup()' closely (as it was meant to). (cherry picked from commit 8ae661048d)		2024-01-15 14:31:06 +02:00
..
include	Recreate listeners on DNS transport change	2024-01-15 14:31:06 +02:00
client.c	Remove unnecessary NULL-checks in ns__client_setup()	2023-10-02 10:04:56 +00:00
hooks.c	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
interfacemgr.c	Fix flawed logic when detecting same listener type	2024-01-15 14:31:06 +02:00
listenlist.c	remove nonfunctional DSCP implementation	2023-01-09 14:23:26 -08:00
log.c	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
Makefile.am	Move all the unit tests to /tests/<libname>/	2022-05-31 12:06:00 +02:00
notify.c	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
query.c	Add new dns_rdatatype_iskeymaterial() function	2024-01-12 19:56:54 +11:00
server.c	Allocate DNS send buffers using dedicated per-worker memory arenas	2023-09-05 15:02:30 +02:00
sortlist.c	De-duplicate __FILE__, __LINE__	2022-10-17 16:00:26 +01:00
stats.c	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
tests	Move all the unit tests to /tests/<libname>/	2022-05-31 12:06:00 +02:00
update.c	Report the type being filtered from an UPDATE	2024-01-13 01:58:57 +11:00
xfrout.c	Adjust comment to have correct message limit value	2023-11-16 12:22:08 +11:00