fix: update getPath to use WHATWG URL API

[mschile]

Additional details

• Updated the getPath method to use the WHATWG URL API.

When processing requests, we set the url using the legacy url API. Since this API is not WHATWG URL API compliant with respect to percent encoding, we receive a path that may be different from what CDP sends causing prerequest correlation timeouts of two seconds.

The following requests were observed in the wild:

With the encoded | as %7C:
https://fonts.googleapis.com/css?family=Roboto+Mono%7COpen+Sans:700&display=swap

Already decoded |:
https://fonts.googleapis.com/css?family=Roboto+Mono|Open+Sans:700&display=swap

Steps to test

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress]

4 flaky tests on run #52397 ↗︎

0

554

6

0

4

Details:

Merge branch 'develop' into mschile/decode_prerequest
Project: cypress	Commit: ad62dfb092
Status: Passed	Duration: 12:48 💡
Started: Nov 20, 2023 7:32 PM	Ended: Nov 20, 2023 7:45 PM

  runs.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
... > displays each run with correct information		Test Replay Screenshots

  cypress-in-cypress.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
Cypress in Cypress > restarts browser if there is a before:browser:launch task and there is a change on the config		Test Replay Screenshots

  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs		Test Replay Screenshots

  debug.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
App - Debug Page > shows running and updating build		Test Replay Screenshots

Review all test suite changes for PR #28354 ↗︎

[cypress-bot]

Released in 13.6.0.

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