TestCafe cannot load website with incorrect headers

What is your Test Scenario?

I’m trying to load https://www.freepeople.com and verify that the page loaded.

What is the Current behavior?

When I’m using node version 12 and above, the page never loads and is stuck at the “about:blank” page. If I use node 10.13.0, the page loads successfully. I am able to load other pages on node version 12, so I’m not sure why this website specifically won’t load.

What is the Expected behavior?

I am expecting the page to load.

What is your web application and your TestCafe test code?

Using node version 12.13.0, and testcafe v1.6.1

 import { Selector, ClientFunction } from 'testcafe';

function getUrl() {
    const clientfunction = ClientFunction(() => document.location.href);
    return clientfunction();
}

fixture('Core Application Tests')

test('Should load the page', async (t) => {
    await t.navigateTo('https://www.freepeople.com');
    await t.wait(3000);
    await t.expect(getUrl()).eql('https://www.freepeople.com');
});

Steps to Reproduce:

1. Run the above code using node version 10.13.0, and testcafe v1.6.1
2. Notice that the website loads correctly
3. Run the above code using node version 12.13, and testcafe v1.6.1
4. Notice that the website never loads, and is stuck on the about:blank page

Your Environment details:

• testcafe version: 1.6.1
• node.js version: 12.13.0
• command-line arguments:
• browser name and version: Chrome, Firefox
• platform and version: macOS 10.14. Also able to reproduce using docker

[LavrovArtem]

This issue relates to node.js that works according to http specification. On the TestCafe side we will fix it in the following way:

• TestCafe will not hang up.
• TestCafe will raise a clear message about this problem: Parse Error: Invalid header value char.

As a workaround, you can revert to the parsing header behavior on Node.js side by passing the NODE_OPTIONS='--http-parser=legacy' environment variable. Thanks @andrzej-kodify.

[Farfurix]

@KingM1

Hello,

Thank you for the detailed information. I’ve reproduced the issue with our testcafe-hammerhead@14.11.1 proxy:

• node@10.13.0 - loaded
• node@10.17.0, node@12.13.1 - didn’t load

Our team will research it and check for a suitable solution.