fix: #29171 set correct host header with fetch

[bjowes]

• Closes Cypress open hangs for a minute or two before loading #29171

Additional details

Use of node-fetch, in particular during launch of the Cypress UI when started with cypress open, did not pass the correct host header to the proxy when accessing HTTPS sites. This affected many corporate proxies that perform HTTPS decryption, resulting in that the requests did not reach their target servers. In addition it caused the launcher to hang.

The implementation is a patch of the node-patch library to set the defaultPort option based on the protocol of the URL. If a specific port is set in the URL, this will still override the defaultPort.

Steps to test

Place cypress behind a proxy that performs HTTPS decryption and launch cypress with npx cypress open.

One such proxy is the ntlm-proxy part of https://github.com/bjowes/cypress-ntlm-auth :

1. Open a terminal, create a testing folder, initiate npm and install cypress-ntlm-auth. Run npx ntlm-proxy. Note the ports used for configApiUrl and ntlmProxyUrl.
2. Open another terminal, configure ntlm-proxy with (make sure to replace xxx with the port from configApiUrl)
   curl -d '{ "ntlmHosts": ["download.cypress.io", "registry.npmjs.org", "on.cypress.io"], "username": "dummy", "password": "dummy", "ntlmVersion": 2 }' -H 'Content-Type: application/json' http://127.0.0.1:xxx/ntlm-config
   The call should return OK.
3. Start cypress with the proxy: HTTP_PROXY=http://127.0.0.1:yyy npx cypress open, make sure to replace yyy with the port from ntlmProxyUrl. The launcher will stall and requests to download.cypress.io, registry.npmjs.org and on.cypress.io will fail.

Repeat step 3 with this PR applied, then the launcher shall work as intended. To test the proxy without HTTPS decryption, simply skip step 2.

How has the user experience changed?

The launcher now works as expected behind proxies that perform HTTPS decryption - for other users no change.

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation? NA - No documentation needs updating
• Have API changes been updated in the type definitions? NA - No APIs have been changed

[cypress-app-bot]

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.

[cypress-bot]

Released in 13.9.0.

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