從仿真器發送請求時的Kestrel錯誤

Question

通過Fiddler向Kestrel發送請求時，以下請求成功。

GET http://192.168.1.148:5000/ HTTP/1.1 
Host: 192.168.1.148:5000 
Connection: keep-alive 

當通過NETMF模擬器發出請求時，以下請求失敗。

GET http://192.168.1.148:5000 HTTP/1.1 
Host: 192.168.1.148:5000 
Connection: keep-alive 

這是ASP.NET Core錯誤消息。該錯誤似乎是關於日誌記錄！

Request finished in 24788.6203ms 500 
fail: Microsoft.AspNet.Server.Kestrel[13] 
An unhandled exception was thrown by the application. 
System.AggregateException: An error occurred while writing to logger(s). 

---> System.ArgumentException: Parameter name: value 

at Microsoft.AspNet.Http.PathString..ctor(String value) 
at Microsoft.AspNet.Http.Internal.DefaultHttpRequest.get_Path() 
at Microsoft.AspNet.Hosting.Internal.HostingLoggerExtensions 
    .HostingRequestStarting.ToString() 
at Microsoft.Extensions.Logging.Console.ConsoleLogger.Log(
    LogLevel logLevel, Int32 eventId, Object state, 
    Exception exception, Func`3 formatter) 
at Microsoft.Extensions.Logging.Logger.Log(
    LogLevel logLevel, Int32 eventId, Object state, 
    Exception exception, Func`3 formatter) 

--- End of inner exception stack trace --- 

at Microsoft.Extensions.Logging.Logger.Log(
    LogLevel logLevel, Int32 eventId, Object state, 
    Exception exception, Func`3 formatter) 
at Microsoft.AspNet.Hosting.Internal.HostingLoggerExtensions 
    .RequestStarting(ILogger logger, HttpContext httpContext) 
at Microsoft.AspNet.Hosting.Internal.HostingEngine 
    .<>c__DisplayClass32_0.<<Start>b__0>d.MoveNext() 

--- End of stack trace from previous location where exception was thrown --- 

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) 
at System.Runtime.CompilerServices.TaskAwaiter 
    .HandleNonSuccessAndDebuggerNotification(Task task) 
at Microsoft.AspNet.Server.Kestrel.Http.Frame 
    .<RequestProcessingAsync>d__79.MoveNext() 

---> (Inner Exception #0) System.ArgumentException: Parameter name: value 

at Microsoft.AspNet.Http.PathString..ctor(String value) 
at Microsoft.AspNet.Http.Internal.DefaultHttpRequest.get_Path() 
at Microsoft.AspNet.Hosting.Internal.HostingLoggerExtensions 
    .HostingRequestStarting.ToString() 
at Microsoft.Extensions.Logging.Console.ConsoleLogger.Log(
    LogLevel logLevel, Int32 eventId, Object state, 
    Exception exception, Func`3 formatter) 
at Microsoft.Extensions.Logging.Logger.Log(
    LogLevel logLevel, Int32 eventId, Object state, 
    Exception exception, Func`3 formatter)<--- 

這是整個ASP.NET Core程序。

using System; 
using Microsoft.AspNet.Builder; 
using Microsoft.AspNet.Http; 
using Microsoft.Extensions.Logging; 

namespace EmptyApplication01 
{ 
    public class Startup 
    { 
     public void Configure(
      IApplicationBuilder app, 
      ILoggerFactory loggerFactory) 
     { 
      loggerFactory.AddConsole(minLevel: LogLevel.Verbose); 

      app.Run(async (context) => 
      { 
       var logger = loggerFactory.CreateLogger("CatchAll"); 
       logger.LogInformation(DateTime.Now.ToString()); 

       await context.Response.WriteAsync("head, body"); 
      }); 
     } 
    } 
} 

Answer 1

關閉日誌記錄修復了這個問題。這可能是ASP.NET日誌記錄實現中的一個錯誤。

using Microsoft.AspNet.Builder; 
using Microsoft.AspNet.Http; 
using System; 

namespace EmptyApplication01 
{ 
    public class Startup 
    { 
     public void Configure(IApplicationBuilder app) 
     { 
      app.Run(async (context) => 
      { 
       // no more logging! 
       System.Console.WriteLine(DateTime.Now.ToString()); 
       await context.Response.WriteAsync("head, body"); 
      }); 
     } 
    } 
} 

Answer 2

我已經想通了。如果AbsoluteURL在路徑中，紅隼將會中斷。爲了使它的工作，這是工作圍繞

app.Use(next => async context => { 

       // get the frame from kestrel and then but the path by removing the hostname 
       var Frame = (Microsoft.AspNet.Server.Kestrel.Http.Frame)context.Features; 

       var newpath = Frame.RequestUri.Replace("http://" + context.Request.Host.Value, ""); 
       context.Request.Path = newpath; 

       // Invoke the rest of the pipeline. 
       await next(context); 

    });