-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Provide support plugin to change electron user agent to exclude electron and cypress details #22953
Labels
topic: cy.origin
Problems or enhancements related to cy.origin command
Comments
AtofStryker
added
the
topic: cy.origin
Problems or enhancements related to cy.origin command
label
Jul 27, 2022
4 tasks
4 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
stage: internal
and removed
stage: routed to e2e-auth
stage: needs review
The PR code is done & tested, needs review
labels
Jul 27, 2022
The code for this is done in cypress-io/cypress#22958, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What would you like?
An official npm support plugin that rewrites the electron user agent to appear more chrome like and avoid blocked requests based on the user agent string.
Why is this needed?
Certain authentication providers 403/block requests coming from Electron user agents based of the
User-Agent
header in the request. Currently, for MacOS devices, the user agent for Cypress Electron looks something like :Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Cypress/0.0.0-development Chrome/100.0.4896.75 Electron/18.0.4 Safari/537.36
Ideally, we want the user agent to read as
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.75 Safari/537.36
when this support plugin is installed to prevent 403s/block requestsOther
No response
The text was updated successfully, but these errors were encountered: