移至IIS7服务器后出现Signalr 404错误

Question

I have a signalr service that is working fine on my development environment when hosted in IIS 8.

When the service is moved to our QA server using IIS 7.5, attempting to connect to my hub results in this error:

System.AggregateException: One or more errors occurred. ---> Microsoft.AspNet.SignalR.Client.HttpClientException: StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
    {
    Cache-Control: private
    Date: Thu, 06 Mar 2014 20:09:35 GMT
    Server: Microsoft-IIS/7.5
    X-Powered-By: ASP.NET
    Content-Length: 5307
  Content-Type: text/html; charset=utf-8
}
   at Microsoft.AspNet.SignalR.Client.Http.DefaultHttpClient.<>c__DisplayClass2.<Get>b__1(HttpResponseMessage responseMessage)
   at Microsoft.AspNet.SignalR.TaskAsyncHelper.<>c__DisplayClass19`2.<Then>b__17(Task`1 t)
   at Microsoft.AspNet.SignalR.TaskAsyncHelper.TaskRunners`2.<>c__DisplayClass3a.<RunTask>b__39(Task`1 t)
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at ConsoleApplication2.Program.Main(String[] args)
---> (Inner Exception #0) Microsoft.AspNet.SignalR.Client.HttpClientException: StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
{
  Cache-Control: private
  Date: Thu, 06 Mar 2014 20:09:35 GMT
  Server: Microsoft-IIS/7.5
  X-Powered-By: ASP.NET
  Content-Length: 5307
  Content-Type: text/html; charset=utf-8
}
   at Microsoft.AspNet.SignalR.Client.Http.DefaultHttpClient.<>c__DisplayClass2.<Get>b__1(HttpResponseMessage responseMessage)
   at Microsoft.AspNet.SignalR.TaskAsyncHelper.<>c__DisplayClass19`2.<Then>b__17(Task`1 t)
   at Microsoft.AspNet.SignalR.TaskAsyncHelper.TaskRunners`2.<>c__DisplayClass3a.<RunTask>b__39(Task`1 t)<---

My Startup class

[assembly: OwinStartup(typeof(SignalRStartup))]

  public class SignalRStartup
  {
    public void Configuration(IAppBuilder app)
    {
      app.MapSignalR("/restricted/signalr", new HubConfiguration());
    }
  }

And attempting to start a connection in the c# client

HubConnection foo = new HubConnection("http://localhost/ccwebdev/restricted");
foo.Start().Wait();

The QA server is running windows server 2008 r2 SP1, so it should have support for extensionless urls.

I also tried adding this to my web.config <modules runAllManagedModulesForAllRequests="true"/>

The app pools are in integrated mode, not classic mode

I have read many other similar SO posts and the troubleshooting guide for 404's here: http://www.asp.net/signalr/overview/signalr-20/troubleshooting-and-debugging/troubleshooting#other , but with no luck.

Can anyone provide any other troubleshooting steps I can try?

---

EDIT

changing my map call to app.MapSignalR("/restricted", new HubConfiguration()); causes an exception to be thrown on service startup

[InvalidOperationException: Protocol error: Unknown transport.]
   Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(HostContext context) +384
   Microsoft.AspNet.SignalR.Hubs.HubDispatcher.ProcessRequest(HostContext context) +502
   Microsoft.AspNet.SignalR.PersistentConnection.ProcessRequest(IDictionary`2 environment) +328
   Microsoft.Owin.Mapping.<Invoke>d__0.MoveNext() +611
   System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
   Microsoft.Owin.Host.SystemWeb.IntegratedPipeline.IntegratedPipelineContext.EndFinalWork(IAsyncResult ar) +208
   System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +434
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288

Answer 1

Did you try to manually patch the server for extensionless URLs? I'm not sure if server 2008 R2 SP1 includes that patch- you can give it a try and see:

http://support.microsoft.com/kb/980368