-
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
Cypress 9.1 appears to mishandle POST content with special characters #19084
Comments
Can confirm this. |
What is strange in my request when I have ~two times in a string, only first one is changed to %5Cx7e second one stays as ~ |
Do you have a reproducible example of this? What app code or test code is running to evidence this? |
I am sending request to authenticate with cy.request and I have ~ in my client secret randomly generated in azure portal and Cypress is trying to encode while creating url for POST |
In my case, I'm seeing it when I try to intercept a request and respond with json data (using req.reply) that contains a I haven't been able to get a reproducible example together yet. |
Hi @chrisbreiding , hi @duck1123 |
The code for this is done in cypress-io/cypress#19239, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Current behavior
Upgraded from 9.0 to 9.1
Multiple Tests that send a POST including random generated password content with blackslashes:
e.g. "oldPassword":"S.]\x7e}gZ3=kFJ" (Note the double backslash - GH editor might hide this!).
Fails at when received at the server as oldPassword is wrong.
Desired behavior
Tests execute POST commands as before.
Test code to reproduce
-UPDATED-
Analysis as in comment below from slavab89 appears to be what I am observing.
Cypress Version
9.1.0
Other
Thank you. 😄
The text was updated successfully, but these errors were encountered: