milanpwc
Created Oct 5, 2021 07:27:39
(0)
(0)
It reports invalid format. The DDNS policy supports: url http://<username>:<password>@api.abc.com/update?hostname=xxx.xxx.xxx username xyz password 123 in http method, but not url https://<username>:<password>@api.abc.com/update?hostname=xxx.xxx.xxx username xyz password 123 in vendor-specific method
fuzi_yao
Reply milanpwc Created Oct 5, 2021 08:48:29
(0)
(0)
bro,We can only configure our URLs in the required format. Example: http://<username>:<password>@update.dyndns.org/nic/update?hostname=<h>&myip=<a> The requirements are as follows: In the URL, <username> and <password> indicate the user name and password, which are in fixed format and cannot be changed. The user name and password in the url request-url username username password password command are automatically filled in. In the URL, <h> and & |
milanpwc
Created Oct 5, 2021 07:27:39
(0)
(0)
It reports invalid format. The DDNS policy supports: url http://<username>:<password>@api.abc.com/update?hostname=xxx.xxx.xxx username xyz password 123 in http method, but not url https://<username>:<password>@api.abc.com/update?hostname=xxx.xxx.xxx username xyz password 123 in vendor-specific method
fuzi_yao
Reply milanpwc Created Oct 5, 2021 08:48:29
(0)
(0)
bro,We can only configure our URLs in the required format. Example: http://<username>:<password>@update.dyndns.org/nic/update?hostname=<h>&myip=<a> The requirements are as follows: In the URL, <username> and <password> indicate the user name and password, which are in fixed format and cannot be changed. The user name and password in the url request-url username username password password command are automatically filled in. In the URL, <h> and & |
|
|