title: Chrome 63 changing http to https
body: <p>Does using Chrome v.63 force use of https?</p>
  
  <p>I am running Apache 2.4.27 on a Windows 10 desktop as a sandbox where I can experiment and do some tutorials.  I have a virtual host setup called www.tutorial.dev with an alias of tutorial.dev.  In the Windows 10 hosts file I have set up www.tutorial.dev and tutorial.dev to point to localhost.  </p>
  
  <p>As of yesterday the url <a href="http://tutorial.dev/Bootstrap4FromScratch/" rel="noreferrer">http://tutorial.dev/Bootstrap4FromScratch/</a> was working normally.  In this case providing a directory listing as a jump off point into various examples and exercises.  Today, when I type in the url Chrome changes it to https and I get a connection refused message.  </p>
  
  <p>I understand the connection refused message.  There are no certificates setup.</p>
  
  <p>The only change I can find is that Chrome changed from v.62.x to v.63.x.  What in Chrome 63 could be forcing http to https?</p>
  
  <p>I don't have this problem with MS Edge.  I tested another similar configuration on a different machine that was in the process of downloading Chrome 63.x.  It already had 62.x installed.  It worked until the 63.x upgrade was complete then the same problem occurred.</p>
  
  <p>Additional information: If I use <a href="http://localhost" rel="noreferrer">http://localhost</a> to bring up the index.html or version.php in the htdocs directory the switch from http to https does not happen.  The virtual host www.tutorial.dev resides in another directory outside of htdocs.</p>
  
  <p>If this has been asked and answered please point me to the question/answer thread.</p>
  
  <p>Thanks in advance,</p>
  
  <p>Barry</p>