You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the Connect tab, under Domain Name, the Web UI seems to enforce HTTP and add a port (as set in the Network tab, usually 8073) to the domain entered. This prevents domain names with HTTPS (e.g. on the standard port 443) from being published on http://kiwisdr.com/public/
To support 3rd party reverse proxies, consider allowing HTTPS and arbitrary ports in the Domain Name URL field, e.g. instead of
my-domain.org => http://my-domain.org:8073
allow entering http:// or https:// and any port, as in
http://my-domain.org:8073 => http://my-domain.org:8073
https://my-domain.org:443 => https://my-domain.org:443
or even https://my-domain.org => https://my-domain.org
Hi,
in the Connect tab, under Domain Name, the Web UI seems to enforce HTTP and add a port (as set in the Network tab, usually 8073) to the domain entered. This prevents domain names with HTTPS (e.g. on the standard port 443) from being published on http://kiwisdr.com/public/
To support 3rd party reverse proxies, consider allowing HTTPS and arbitrary ports in the Domain Name URL field, e.g. instead of
allow entering http:// or https:// and any port, as in
(This seems to require a relatively small change in https://github.com/jks-prv/Beagle_SDR_GPS/blob/master/web/kiwi/admin.js but I'm not a JS expert.)
Kind regards, Thomas
The text was updated successfully, but these errors were encountered: