Well...

I've got back home and I've found something I don't like AT ALL.

I'll put it simple.  Why does the resulting web page of my website page is the router login access page even if I set port forwarding to another machine when a traffic from port 80 is coming and even if I also set port,like, 1234 for management purposes?

I've found this when connected to my wifi home network.

In simple words, it looks like the port 80 is reserved to the router management routine, regardless of any other rule you set. Even if you set a different port for that. 

This means that this router does not allow customers to set up a web server, since port 80 can't be used. This is also conflicting with the nat forwarding menu which by default sets port 80 for http services, but this port forwarding won't be triggered at all.

If I am right,  and I hope I'm not,  this is a severe and very disappointing bug.

Any thoughts?

@Kevin_Z hi Kevin,

Thanks for your reply.

As I said, I've already changed the port for management into a different number.

And the port 80 is still unavailable for port forwarding.

Even if I change the port for local management to another number,the port 80 is still locked and it points to the router access page!

May I kindly remind you I paid 140€ for this product which is not working as described in your manual.

It's quite clear right now that you do not test your products before launching in the market. 

In addition, I've found several other posts with same issue involving other products of yours ,thus demonstrating tp link has no intention, or maybe capabilities, to address this severe issue. But you still sell your routers as capable of doing port forwarding, which is not actually the truth.

It would at least be honest from your side to provide a firmware update to address your bugs.