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 d50d981543)
pull/886/head
parent
309ec5e762
commit
faf4c3b5d3
Loading…
Reference in new issue