The main reason is explained in this reply on Stackoverflow here: https://stackoverflow.com/questions/25277457/google-chrome-redirecting-localhost-to-https
My problem came from having a .dev domain, which was apparently recently registered as a gTLD and put in a commit to Chrome Canary. I found this out from a recent post I came across as I searched for my problem. If you have the same problem I do, it appears that the best solution is to change your domain to be something other than .dev. The article suggested .test with a potential solution of .localhost later down the road (via this proposal).