Cypress 9.1 open wrong URL when there is a ~ (tilde) in the link

[lephuongbg]

Current behavior

In Cypress 9.1, some of our tests failed due to Cypress process the URL in visit() calls incorrectly.

This code:

cy.visit('/?q=~%28match_status~%28~%27invoiced%29%29')

causes Cypress to visit this link:

/?q=%5Cx7e%28match_status~%28~%27invoiced%29%29

Note the strange %5Cx7e right after the q=.

Desired behavior

Cypress should not alter the visit URL in anyway.

Test code to reproduce

https://github.com/lephuongbg/cypress-test-tiny/tree/cypress-9.1-url-bug

Quick link to diff:

cypress-io/cypress-test-tiny@master...lephuongbg:cypress-9.1-url-bug

Cypress Version

9.1.0

Other

No response

[lephuongbg]

These also look like the same issue:

#19084
#19115
#19096

[chrisbreiding]

Thanks for the report and the reproduction. This appears to be a regression, so we'll look into addressing it.

[Narretz]

Hi @chrisbreiding while you're investigating: it appears that this issue also affects requests via cy.request(): #19084

(Fixing one will probably fix the other because both use the cypress-request lib?)

[chrisbreiding]

(Fixing one will probably fix the other because both use the cypress-request lib?)

I think you're right. Here's all the other issues so far reporting this for various commands:

• Cypress 9.1 appears to mishandle POST content with special characters #19084
• Bad body encoding in cy.request #19115
• setCookies is broken since 9.0.0. ~ is converted to \x7e  #19096
• cy.intercept fails to respond with JSON containing tilde (~) in string property #19178

[barboramartinkova]

We have the same problem with writing a response body into a fixture file, it converts ~ into \7x and then when cypress tries to read from that fixture, it's throwing an error that it's an invalid JSON because of the \ char 😢

[cypress-bot]

The code for this is done in cypress-io/cypress#19239, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 9.1.1.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v9.1.1, please open a new issue.