I was incorrect in the fact of the OP's error message, and I see along with the above folks who replied, that it has to do with sending the loginname/password direct in the URL- Wheelman - check your URL it might be malformed in the address bar
However, on SSL, the fact still remains: Mozilla and Chrome are both planning to deprecate HTTP.
It is a gradual phaseout, but it is happening as we speak. Chrome already is telling me that "This site is not secure". The warning will become more prominent in future version.
Luckily, SSL Certs have come down quite a bit in price...they will probably come down more soon. You can get them for around $50/year.https://threatpost.com/chrome-to-la...2017/120452/http://motherboard.vice.com/read/go...chrome-httpshttps://blog.dareboost.com/en/2016/...our-website/
Chrome users who navigate to some HTTP sites will be notified, starting in January, they're on a site that isn't secure.
Google said today the browser will begin explicitly labeling HTTP connections that feature either a password or credit card form as non-secure. The company said the plan is its first step toward marking all HTTP sites as non-secure, though it didn't provide a timetable for the undertaking.