title: HTTP served page marked as insecure in chrome
body: <p>As of January Chrome will show it's users that a site is being insecure if it contains either a password or credit-card field and isn't served via https. (see <a href="https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html" rel="nofollow noreferrer">https://security.googleblog.com/2016/09/moving-towards-more-secure-web.html</a> )</p>
  
  <p>This circumstance raises a little problem: 
  When you have a web service running locally (for example the web-login page of your router at home ) which is not served with HTTPS since there is the strong possibility that the certificate will expire before the user updates it's software, your user will see this warning.</p>
  
  <p>Mocking the password-field seems too hacky and will likely cause problems on mobile devices. </p>
  
  <p>What would be good alternatives to solve this problem without serving the site with HTTPS?</p>