I know it would be handy if supported, but actually what happens is that you are attempting to access the router itself on port TCP 8080 on ip address associated with WAN interface from internal LAN: it doesn't trigger the NAT translation so it doesn't work.
You can check this with show ip nat translations or even with debug ip nat
From networking point of view you should use private IP address when you are in the private internal network=LAN, that is the way NAT is designed to work.
this not possible because hairpinning ( the feature you want to use) is not implemented on Cisco routers but DNS rewrite also called DNS doctoring should be implemented and so if this is the case you must have a public DNS server with your A record on it and then you will access the server with its FQDN either from outside or inside( in which case the router will rewrite the DNS reply to the inside IP address of the server).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...