MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Webview2 is now detectable by security firewalls when data scraping

Open
#4,444 1 comment 0 reactions 2 assignees View on GitHub

@vbryh-msft is already working on this.

Since Mar 23, 2024.

bug regression
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

Hi,
I have been using webview2 for years for web scraping without being detected but with the new 123.0.2420.53 version it is now detectable, I do not know if by headers or something different but I cannot use it anymore on the site I used to use for a long time. My app is still working fine with older versions. I mean everything is fine but firewalls are somehow understand it and block it. Could you please revert what you have done? At first look Accept-Encoding header comes with different parameters but I cannot change it because they can still block I think you have changed many things and now they can easliy understand it is not the Edge browser, previous versions did not have this issue and they cannot differ it from the Edge browser.
Kind regards

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

123.0.2420.53

SDK Version

No response

Framework

Winforms

Operating System

Windows 10

OS Version

10.0.19045 Build 19045

Repro steps

Nothing just run it and they can somehow differ it from the Edge browser but they cannot do it with previous versions cause the code still works fine with previous versions of Webview2

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Regression in newer Runtime

Last working version (if regression)

122.0.2365.92

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.