-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
[Bug]: zscaler detecting scripts running as old version of chrome and blocking them from executing #642
Comments
Recommend we update UserAgent used in various functions to align to the Microsoft Edge user agent |
This is included in the |
Will do when I return to the office next week
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Aaron Parker ***@***.***>
Sent: Tuesday, April 9, 2024 4:06:37 AM
To: aaronparker/evergreen ***@***.***>
Cc: sarjent ***@***.***>; Author ***@***.***>
Subject: Re: [aaronparker/evergreen] [Bug]: zscaler detecting scripts running as old version of chrome and blocking them from executing (Issue #642)
This is included in the 2404.901 release. Could please test and see what the result is?
—
Reply to this email directly, view it on GitHub<#642 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AIOUBVJKRSK7SH3UBUO6BWDY4OVR3AVCNFSM6AAAAABE62YO4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBUGUYDMNJVGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi Set it to version 122 does not realy solve the problem as this version is already old, too - my customer has zscaler to block chrome older than 123.x -> 122 was blocked. |
What happened?
error that the scripts have been blocked by zscaler for emulating chrome v7. need to be able to use edge or emulate a more recent version of chrome
Version
2403.889
What PowerShell edition/s are you running Evergreen on?
Windows PowerShell
Which operating system/s are you running Evergreen on?
Windows Server 2016+
Have you reviewed the documentation?
Verbose output
The text was updated successfully, but these errors were encountered: