MicrosoftEdge / MicrosoftEdge/WebView2Samples

_webView2.CoreWebView2.WebResourceResponseReceived is not invoked

Open
#164 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
1k
Forks
521
Avg merge
13m
Merged PRs (30d)
1

Description

My application works fine on my laptop (Windows 10).

When the application runs on my dev VM (Windows Server 2016), the interaction with the Web server and rendering of web pages are all good, and the request and response messages exchanged with the Web server are captured by Fiddler; however, _webView2.CoreWebView2.WebResourceResponseReceived is not invoked.

The version of "Microsoft.Web.WebView2" package is "1.0.1418.22". The runtime version is the same on both machines:
image

        private void CoreWebView2Ready(object sender, EventArgs e)
        {
            _webView2.CoreWebView2.WebResourceRequested += WebResourceRequested;
            _webView2.CoreWebView2.WebResourceResponseReceived += ResponseReceived;
            _webView2.CoreWebView2.ClientCertificateRequested += ClientCertificateRequested;

            _webView2.CoreWebView2.Settings.AreHostObjectsAllowed = false;
            _webView2.CoreWebView2.Settings.IsWebMessageEnabled = false;
            _webView2.CoreWebView2.Settings.AreDefaultScriptDialogsEnabled = false;

            _webView2.Source = new Uri(SsoEndpointUrl);
        }

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CoreWebView2Ready entry point shown in the report and review the WebResourceResponseReceived event setup. Compare behavior on Windows 10 and Windows Server 2016 using Microsoft.Web.WebView2 1.0.1418.22, with Fiddler confirming traffic. Done means identifying a reproducible cause for the missing event or documenting that the issue cannot be reproduced.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.