No working workaround for : Native Automation requires https protocol

[wombatka]

What is your Scenario?

I cannot run my tests over http using native automation and chrome 130,
I tried using workaround from: #8133
The url seems to be loaded via http but it is not which can be seen in the browser console

What is the Current behavior?

automatic redirect to https occurs and page is not loaded

What is the Expected behavior?

page should be loaded via http

What is the public URL of the test page? (attach your complete example)

example.js:

import {Selector, t} from "testcafe";

fixture('MWE')
test('Website served only by HTTP is tried to be opened with HTTPS', async () => {
await t.navigateTo('http://www.testingmcafeesites.com/')
await t.debug()
})

What is your TestCafe test code?

example.js:

import {Selector, t} from "testcafe";

fixture('MWE')
test('Website served only by HTTP is tried to be opened with HTTPS', async () => {
await t.navigateTo('http://www.testingmcafeesites.com/')
await t.debug()
})

package.json

{
"name": "testcafeexample",
"version": "1.0.0",
"description": "",
"main": "example.js",
"scripts": {
"test": "testcafe chrome example.js"
},
"author": "",
"license": "ISC",
"dependencies": {
"testcafe": "3.7.0-rc.2"

}
}

customRequestHook.js

const RequestHook = require('testcafe').RequestHook
class CustomRequestHook extends RequestHook {
constructor (requestFilterRules) {
super(requestFilterRules);
}

onRequest(e) {
    console.log("Changing protocol")
    e.requestOptions.protocol = 'http:';
}

.testcaferc.cjs

let CustomRequestHook = require('./customRequestHook.js').CustomRequestHook
const hook = new CustomRequestHook(/https?://.*/);
module.exports = {
hooks: {
request: hook
},
skipJsErrors : true
}

onResponse(e) {
}

}

module.exports = {
CustomRequestHook
}

Your complete configuration file

let CustomRequestHook = require('./customRequestHook.js').CustomRequestHook
const hook = new CustomRequestHook(/https?://.*/);
module.exports = {
hooks: {
request: hook
},
skipJsErrors : true
}

Your complete test report

No response

Screenshots

Steps to Reproduce

1.run test
2.open browser console
3.you will see that requet was sent with https not http

TestCafe version

3.7.0-rc.2

Node.js version

21.7.1

Command-line arguments

npm test

Browser name(s) and version(s)

chrome 130

Platform(s) and version(s)

Ubuntu 22.04.2 LTS

Other

No response

[wombatka]

you can see in network console that origin is set to url with https, despite custom hook i used

[github-actions]

We appreciate you taking the time to share information about this issue. We reproduced the bug and added this ticket to our internal task queue. We'll update this thread once we have news.

[wombatka]

Any updates here? We cannot update chrome because of this issue..

[aleks-pro]

Hello @wombatka ,

We are researching the issue. We will update this thread once we have news.

[Bayheck]

Hello,

I researched the issue further, and here is what I found.

For some reason, the HTTP request event fails to arrive quickly enough to execute the customHook onRequest method. To address this, I introduced a delay before changing the protocol, and everything now works as expected.

You can verify the origin of the page in the DevTools console by checking either window.location.origin or window.location.protocol.

This is the updated workaround for your case:

async onRequest(e) {    
    await new Promise(resolve => setTimeout(resolve, 5000)); //you can increase this value if issue persists.

    e.requestOptions.protocol = 'http:';
}

Please try this solution and let us know your results.

[wombatka]

Hi. I checked - introducing a delay of minimum 1s works for me. however delay on each request makes the whole test run ( we have over 1500 tests) significanlty slower

[wombatka]

Additionally download files does not work over http- chrome shows insecure download warning and there is no way to switch it off (previously working flags were removed)

[Bayheck]

Additionally download files does not work over http- chrome shows insecure download warning

Hello, could you please share an example of this behavior so we can reproduce it on our side?

[Bayheck]

Hello, I have found a flag that seems to cause the issue.

Try to run your tests with the following command:

testcafe "chrome --disable-features=HttpsUpgrades" test.js

With this feature disabled, you do not need the custom hook workaround.

Please try running your test with this flag and let us know your results.

[wombatka]

Hi. This flag works without a custom hook for me , thank's!
I also found a solution for the download confirm dialog that shows when you download from an http domain:
--unsafely-treat-insecure-origin-as-secure=yourDomain
There used to be a feature flag to disable the warning dialog- --disable-features=InsecureDownloadWarnings but in Chrome 130 it is removed

[wombatka]

Additionally download files does not work over http- chrome shows insecure download warning

Hello, could you please share an example of this behavior so we can reproduce it on our side?

Unfortunatelly i cannot share a link to our test installation as it is our internal network. I am not sure whether you can find an example domain to reproduce it- this issue occurs when you click some action that downloads a file from a http domain other than localhost on chrome 130.
Instead of downloading a file automaticaly- unconfirmed download dialog appears, asking if you want to keep the file or not
In older chrome you could swith this dialog off now you cannot

[EmilIfrim]

Seems that chrome --disable-features=HttpsUpgrades has been removed. Is there a workaround for this?

https://superuser.com/questions/1836968/google-chrome-has-now-removed-the-https-upgrades-flag-how-do-you-prevent-http

[Bayheck]

Hello,

I did not manage to reproduce the issue with this workaround.

Could you please confirm that you are able to reproduce the issue with "--disable-features=HttpsUpgrades"?

[EmilIfrim]

Sorry, my bad. i cannot repoduce it either, but I was expectingto see this flag under :

1. chrome://flags/
2. https://peter.sh/experiments/chromium-command-line-switches/

[Bayheck]

Hello,
While the flag is not listed, it must exist internally. Otherwise, the workaround won't work.
Please open a separate ticket if any issues arise with HTTP.

[github-actions]

This issue was automatically closed because there was no response to our request for more information from the original author. Currently, we don't have enough information to take action. Please reach out to us if you find the necessary information and are able to share it. We are also eager to know if you resolved the issue on your own and can share your findings with everyone.