title: Socket.io inconsistent Cross Domain Request Error?
body: <p>I have a request from <a href="https://example.com" rel="nofollow">https://example.com</a> to <a href="https://example.com:8080" rel="nofollow">https://example.com:8080</a> which works here, however on another network and on a 4Glte network connection I get an error that <a href="https://example.com" rel="nofollow">https://example.com</a> cannot read the message from example.com:8080/socket.io/.</p>
  
  <p>I've setup my .htaccess to allow cross domain requests from the same domain, like this:</p>
  
  <pre><code>&lt;IfModule mod_headers.c&gt;
      &lt;FilesMatch ".*$"&gt;
          Header set Access-Control-Allow-Origin https://example.com
          Header set Access-Control-Allow-Origin https://example.com:8080
          Header set Access-Control-Allow-Origin http://example.com
          Header set Access-Control-Allow-Origin http://example.com:8080
      &lt;/FilesMatch&gt;
  &lt;/IfModule&gt;
  </code></pre>
  
  <p>And although this works from one connection, it doesn't work from the others. Why could this be?</p>