title: Prevent Chrome-Headless from enforncing ssl
body: <h2>Setup</h2>
  
  <p>I'm running chrome-headless as a container in my docker-compose project. My main app (the one I'd like to test) is named 'app' inside the compose file.</p>
  
  <p>To connect from the chrome-headless container to my app, I'm using the dockers internal containerlinking: <a href="http://app:3000" rel="nofollow noreferrer">http://app:3000</a></p>
  
  <p><strong>docker-compose.yml</strong></p>
  
  <pre><code>version: '3'
  
  services:
    app:
      build:
        context: .
      ports:
        - 3000:3000
  
    chrome:
      image: alpeware/chrome-headless-trunk
  </code></pre>
  
  <h2>Problem</h2>
  
  <p>While this should be easy going, there is one detail, that makes things complicated: chrome-headless is enforcing ssl on ".app" domains. Since I'm connecting to '<a href="http://app:3000" rel="nofollow noreferrer">http://app:3000</a>' this rule applies.</p>
  
  <p>When connecting I get this error:</p>
  
  <blockquote>
  <pre><code>net::ERR_SSL_PROTOCOL_ERROR at http://app:3000
  </code></pre>
  </blockquote>
  
  <h2>Question</h2>
  
  <p>Is there any way to setup chrome-headless to stop enforcing ssl on certain domains?
  <strong>Changing the name from 'app' to something else in the docker-compose.yml</strong> actually works, but this seems like a rather ugly workaround.</p>
  
  <p>Thank you</p>