3
Votes

Implementing 'HTTP Referer Head Check' WebGUI option for remote administration

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
 
3
Votes

Implementing 'HTTP Referer Head Check' WebGUI option for remote administration

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Implementing 'HTTP Referer Head Check' WebGUI option for remote administration
Implementing 'HTTP Referer Head Check' WebGUI option for remote administration
2022-03-19 13:40:32 - last edited 2022-03-19 13:42:47
Model: Archer AX20  
Hardware Version: V1
Firmware Version: Archer AX20(EU)_V1_211231

When the router is behind NAT already (double NAT) after remote login attempt to the WebGUI, the browser redirects to the tplinkwifi.net local URL and the router's WebGUI goes inaccessible.

If 'HTTP Referer Head Check' is implemented and disabled then the one should be able to access the router's WebGUI remotely.

 

 

 

 

If this was helpful click once on the arrow pointing upward. If this solves your issue, click once the star to mark it as a "Recommended Solution".
#1
Options

Information

Helpful: 3

Views: 580

Replies: 0

Voters 2

voter's avatar
voter's avatar