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: #551pull/604/head
parent
8eb6a329d6
commit
d50d981543
Loading…
Reference in new issue