FS#3356 - https-dns-proxy: Luci interface breaks the configuration if a custom server is used #8210
Labels
core packages
pull request/issue for core (in-tree) packages
flyspray
release/19.07
pull request/issue targeted (also) for OpenWrt 19.07 release
Nowaker:
When you edit
/etc/config/https-dns-proxy
and set a custom server, not known to Luci HTML interface, the Luci UI at /cgi-bin/luci/admin/services/https-dns-proxy will display "CIRA Canadian Shield (Family)" as the selected resolver. This, by itself is not a problem yet, as the Proxy will function as expected.However, the moment one makes any changes in the UI, e.g. changing listen port,
/etc/config/https-dns-proxy
will get rewritten and an actual resolver for CIRA Canadian Shield (Family) will be used.Luci interface for HTTPS DNS Proxy should:
resolver_url
,bootstrap_dns
,user
andgroup
propertiesThe problem applies on any device as it's not device-specific.
Reproduction instruction:
/etc/config/https-dns-proxy
and make it look like this:/etc/config/https-dns-proxy
loseresolver_url
setting.The text was updated successfully, but these errors were encountered: