title: SignalR on IIS 7.5 always uses Long Polling with every Browser
body: <p>I know SignalR has it's transport-method hierarchy: Websocket->Server-Sent Events->Forever Frame->Long Polling</p>
  
  <p>But when I check the console in every Browser, I noticed that the transport is <strong>always</strong> Long Polling.</p>
  
  <p>I'm using Windows 7, IIS Express 7.5 and Visual Studio 2013 (SignalR 2.0 of course).</p>
  
  <p>I know Websocket is only supported with IIS 8, but at least SSE or Forever Frame for IE should work.</p>
  
  <p>For example in Google Chrome I get this:
  <img src="https://i.stack.imgur.com/ewckC.png" alt="enter image description here"></p>
  
  <p>That means, Chrome is trying to use SSE right? But why is it cancelled?</p>
  
  <p>And here a screenshot of Fiddler with Internet explorer:</p>
  
  <p><img src="https://i.stack.imgur.com/ipdHb.png" alt="enter image description here"></p>
  
  <p>It's blue... and the code is 200. (and why are there different ports? The site runs under port 4040, but where does 11437 come from?)
  There isn't even an explanation, why IE doesn't go on using SSE.</p>
  
  <p>I mean, SSE/Forever Frame <strong>does</strong> work with IIS 7.5, doesn't it?</p>
  
  <p>Thank you in advance!</p>
  
  <p>PS: Before you ask, I am at home and not behind a proxy</p>