> no ssl certificate because?
This is way beside the point but there is nothing inherently wrong with unsecured plain http traffic if you aren't accepting user information over that connection (such as a name/password, auth token or whatever).
This is way beside the point but there is nothing inherently wrong with unsecured plain http traffic if you aren't accepting user information over that connection (such as a name/password, auth token or whatever).
There are also networking policies that prevent non-https connections, so you could be accidentally blocking out users on a strictly managed device.