Faq

Frequently Asked Questions

• Why doesn't SignalR work in browser X?

  SignalR requires a JSON parser and ability to send xhr requests (for long polling). If your browser has none, you'll need to include json2.js in your application (SignalR will throw an error telling your you need it as well). You can get it on NuGet.

• Why does signalr/hubs return 404?

  If you're writing an MVC application, make sure that you are using Url.Content for your script references:

<script type="text/javascript" src="@Url.Content("~/signalr/hubs")"></script>

If you're writing a regular ASP.NET application use `ResolveClientUrl` for your script references:

<script type="text/javascript" src='<%= ResolveClientUrl("~/signalr/hubs") %>'></script>

If the above still doesn't work, make sure you have RAMMFAR set in your web.config:

<configuration>
   <system.webServer>
        <modules runAllManagedModulesForAllRequests="true">
        </modules>
    </system.webServer>
</configuration>

• Why do I get an exception saying "Unknown Transport" on the server side?

Make sure you're using the latest version of the signalr client (js or .net client).