Native Automation requires https protocol

[czarekeltonjohn]

What is your Scenario?

We have web applications deployed on internal k8s cluster available by http protocol. Is there any configuration or flag that will allow testcafe v.3.5.0 with native automation enabled to reach such web app using http protocol. We can omit ssl certificate errors using chrome flag, but it seems testcafe is allowing only https (which in my case is always unreachable). Even if I explicetely set page as "http://" in testcafe browser it is "https://"

What are you suggesting?

Configuration change or flag that will allow native automation using http protocol

What alternatives have you considered?

No response

Additional context

No response

[PavelMor25]

Hello @czarekeltonjohn,

TestCafe allows you to open HTTPS and HTTP/2 websites in Native Automation mode out of the box. Please share a minimal working example so that the TestCafe team can research the issue and help you.

[czarekeltonjohn]

Hi, let me share with you with my minimal working example.

.testcaferc configured to ignore ssl errors and enable native automation for sure

{
  "browsers": "chrome --ignore-certificate-errors",
  "disableNativeAutomation": false
}

test.ts with test of navigating to website served only by http, site cannot be opened because testcafe browser tries to open it by https

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()
})

[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.

[PavelMor25]

Hello @czarekeltonjohn,

We have investigated this issue and found a workaround for it. Since requests in Chrome are automatically upgraded to HTTPS in Native automation, you can create a custom request hook that will intercept request and change the protocol back to HTTP. Then, you can either define it globally in the configuration file or use it at the fixture or test level.

customRequestHookFile.js:

import { RequestHook } from 'testcafe';
 
export default class CustomRequestHook extends RequestHook {
    constructor (requestFilterRules) {
        super(requestFilterRules);
    }

    onRequest(e) {
        e.requestOptions.protocol = 'http:';
    }

    onResponse(e) {
    }
}

configuration file:

import CustomRequestHook from './hook.js'

const hook = new CustomRequestHook(/https?:\/\/www.testingmcafeesites.com/)

module.exports = {
    hooks: {
        request: hook
    }
}

Please let us know your results.

[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.

[wombatka]

I have the same issue- tried using you workaround but it does not work fully- my url is opened via http - which is ok, but after i login to the application ( I am using Roles) - nothing is loaded- please provide a working workaround. It is critical for me - currenrly all our tests are failing
In console I can see:

But the page was loaded via http so something is not ok here

[PavelMor25]

Hello @wombatka,

Could you please create a separate ticket for the issue and share a minimal working example? This will help the TestCafe team investigate the issue in greater detail.

[wombatka]

Hello @wombatka,

Could you please create a separate ticket for the issue and share a minimal working example? This will help the TestCafe team investigate the issue in greater detail.

created new issue: #8330