Open wh1sp3r opened 5 years ago
I can confirm. Weak ETags are not handled correctly. Here is the stack trace.
Microsoft.Net.Http.Headers.dll!Microsoft.Net.Http.Headers.EntityTagHeaderValue.EntityTagHeaderValue(Microsoft.Extensions.Primitives.StringSegment tag, bool isWeak) Line 57 Microsoft.Net.Http.Headers.dll!Microsoft.Net.Http.Headers.EntityTagHeaderValue.EntityTagHeaderValue(Microsoft.Extensions.Primitives.StringSegment tag) Line 37 Microsoft.VisualStudio.Web.BrowserLink.dll!Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleWareUtil.AddToETag(Microsoft.AspNetCore.Http.Headers.ResponseHeaders responseHeader, int port) Line 82 Microsoft.VisualStudio.Web.BrowserLink.dll!Microsoft.VisualStudio.Web.BrowserLink.BrowserLinkMiddleware.ExecuteWithFilter.AnonymousMethod__0() Line 109
I can confirm I had the same problem with the .Net 5.0 "ASP.Net Core + Angular" template with BrowserLink in VS2019.
I'm also running into the same issue in ASP.Net Core + Angular. Is there a workaround available yet?
Hi,
I found a problem with browserlink. Using browserlink shows "System.ObjectDisposedException: The response has been aborted due to an unhandled application exception. ---> System.FormatException: Invalid ETag name"
Repo: