mirror of https://github.com/asterisk/asterisk
Currently, a reload will always occur if the
Reload header is provided for the UpdateConfig
action. However, we should not be doing a reload
if the header value has a falsy value, per the
documentation, so this makes the reload behavior
consistent with the existing documentation.
Resolves: #551
(cherry picked from commit 874ee6e9aa
)
releases/21.9
parent
e65c8cede5
commit
dd90d4536f
Loading…
Reference in new issue