Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Browserlink & React template #86

Open
wh1sp3r opened this issue Dec 3, 2018 · 3 comments
Open

Browserlink & React template #86

wh1sp3r opened this issue Dec 3, 2018 · 3 comments

Comments

@wh1sp3r
Copy link

wh1sp3r commented Dec 3, 2018

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:

  1. Create Asp net core website
  2. Select React template
  3. Install browserlink from nugget
  4. Add app.UseBrowserlink() into configure method
  5. Run and access the page.
@nesherhh
Copy link

nesherhh commented Apr 17, 2019

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

@swythan
Copy link

swythan commented Feb 10, 2021

I can confirm I had the same problem with the .Net 5.0 "ASP.Net Core + Angular" template with BrowserLink in VS2019.

@mrjfalk
Copy link

mrjfalk commented Oct 27, 2021

I'm also running into the same issue in ASP.Net Core + Angular. Is there a workaround available yet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants