Tested and confirmed, happens only on the docs pages and not on the API itself. Port 8080 is a port without TLS configured, hence it should return errors if you try to connect to it over https.
It's likely your browser that upgrades the connection to https automatically, which is good, otherwise you would have accessed a non encrypted version of the site.
Cause of the problem
Some urls in API docs pointed to the non https version of the docs.
API docs has been upgraded, and the bad urls has been replaced. It should now route to https over port 443 and provide an encrypted connection. Make sure to double check and let me know if the problem comes back.