You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We added Mvp.Xml as a dependency in our ASP.NET Web API, which caused a net::ERR_HTTP2_PROTOCOL_ERROR on startup when application was started on a server without internet access. When we removed the package from the application dependencies, the application started without issue. My suspicion is that the Mvp.SponsorLink package is calling home even though the documentation says it won't. Another thought is that the System.Net.Http.WinHttpHandler package, which SponsorLink requires, is checking to see if HTTP/2 is supported on the host.
Steps to Reproduce
Run a ASP.NET application in IIS 10
Expected Behavior
Application startup is successful
Exception with Stack Trace
Client did not give us the full stack trace.
Version Info
v3.0.0
Additional Info
We don't run into the same issues when we run the app on a server with internet access.
The text was updated successfully, but these errors were encountered:
Describe the Bug
We added
Mvp.Xml
as a dependency in our ASP.NET Web API, which caused a net::ERR_HTTP2_PROTOCOL_ERROR on startup when application was started on a server without internet access. When we removed the package from the application dependencies, the application started without issue. My suspicion is that theMvp.SponsorLink
package is calling home even though the documentation says it won't. Another thought is that theSystem.Net.Http.WinHttpHandler
package, which SponsorLink requires, is checking to see if HTTP/2 is supported on the host.Steps to Reproduce
Run a ASP.NET application in IIS 10
Expected Behavior
Application startup is successful
Exception with Stack Trace
Client did not give us the full stack trace.
Version Info
v3.0.0
Additional Info
We don't run into the same issues when we run the app on a server with internet access.
The text was updated successfully, but these errors were encountered: