title: HSTS workaround for Chrome for Dev Environment
body: <p>We are looking for a way to have Chrome bypass the HSTS requirements for our dev environment.  </p>
  
  <p>We are working on a project for <a href="https://foo.com" rel="noreferrer">https://foo.com</a>. </p>
  
  <p>Within our organizations internal dns we have DNS entries for foo.com.dev which points to our internal dev server which has historically allowed us to reach our dev server via <a href="https://foo.com.dev" rel="noreferrer">https://foo.com.dev</a>.  Secure web requests to this site have always been met with a security warning that we have been able to bypass but in a recent build of Chrome it seems that the ability to bypass the warning has been removed.  We can continue to use this method in IE but would like to be able to test Chrome as well.  </p>
  
  <p>Additionally, developers have been able to use there own machine names as suffixes.  For example a <a href="https://foo.com.workstation10" rel="noreferrer">https://foo.com.workstation10</a></p>
  
  <p>Any suggestions would be very welcome because the prospect of reconfiguring our entire dev environment is not a pleasant one. </p>
  
  <p>To be clear - access to these sites are entirely limited to internal users by both firewall setup and dns configuration. </p>