BUG?: custom DDNS config is ignoring https://
BUG?: custom DDNS config is ignoring https://
Tags:
#DDNS
hi all,
I wanted to go away from my previous DDNS provider coding my own API, but it seems, there is apparently a bug.
Even if the URL contains https://
it is apparently ignored as I get always http response 301 - moved permanently - which occurs when I try to access the API via plain http://.....
any idea? did I something wrong or is this a bug?
/BR
ZoloNN
-----------------------------------------------------------------------
Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0
CET (GMT+1)
Re:BUG?: custom DDNS config is ignoring https://
Hi @Gabriel-TP,
answers can be found in the thread header and in text, but to summarize (I've added the Gateway info too):
- Controller type: Windows version
- Software version: 6.2.10.15
- Gateway type: ER605 v2.0
- Gateway FW: 2.3.3
- DDNS provider: my own API on my webserver written in PHP
bug symptoms:
even the URL contains "https://" (see picture above) I receive "301 - Moved Permanently", which occurs when accessing via plain unencrypted "http://"
(which sane person sends unencrypted username/password via public internet????)
proof:
/BR
ZoloNN
-----------------------------------------------------------------------
Omada 2x ER605(UN) v2.0 + SG2008P(UN) V3.20 + SG2218 V1.20 + 2x SG2008 V4.20 + 3x EAP615-Wall(EU) V1.0
CET (GMT+1)