"rndc reconfig" does not reload http statements

Summary

When we add an endpoint in an http statement in named.conf and run rndc reconfig, the new endpoint is not effective.
Bind needs to be restarted for the endpoint to be effective.
The reconfig was working in 9.18.2.

BIND version used

Bug introduced in 9.18.3 BIND 9.18.3 (Stable Release) id:16aefa3

Steps to reproduce

1. Bind is started as an http server:

http local-http-server {
    endpoints {
        "/endpoint1/dns-query";
    };
};

option {
    ...

    listen-on port 8443 tls tls_conf http local-http-server {any;};

    ...
}

2. Add an endpoint in named.conf :

http local-http-server {
    endpoints {
        "/endpoint1/dns-query";
        "/endpoint2/dns-query";
    };
};

3. Run rndc reconfig

What is the current bug behavior ?

Configuration is not reloaded, the new endpoint responds with 404 error.

What is the expected correct behavior?

Configuration is reloaded, the new endpoint responds to dns queries.