title: Socket.io angularjs client not connected due to CORS error
body: <p>I recently ported an app over from Ionic framework. My app utilized socket.io, which worked flawlessly in ionic.</p>
  
  <p>It does not work properly in steroids / supersonic. I am getting the following when the client tries to connect to my nodejs server using socket.io:</p>
  
  <pre><code>Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true.
  </code></pre>
  
  <p>Why am I getting this in supersonic when I did not have this error in ionic? Currently the server has the following in .htaccess:</p>
  
  <pre><code>Header set Access-Control-Allow-Origin http://localhost:8100
  </code></pre>
  
  <p>My socket.io script is loaded in <code>common/layout.html</code> which means it gets loaded with all views in the app.</p>
  
  <p>The node.js server has not changed and is configured similar to the basic <a href="http://socket.io/docs/" rel="nofollow">socket.io docs</a>.</p>
  
  <p>I am stumped. There are a million and one posts around the net about this particular error with a million and one suggestions on how to fix......none of which has helped me solve this. Since this is a mobile hybrid app, there won't be an origin sent from the client when the app is running on a real device. But for now I am on the iOS emulator and using Safari inspector to see why I can't keep a socket.io connection.</p>
  
  <p>I have tried to use the express cors package and other method to override the '*' wildcard setting with a specific origin:</p>
  
  <pre><code>http://localhost:8100
  </code></pre>
  
  <p>Nothing seems to help.</p>