Return null response on page with redirect

I checked many similar issues including #2479 #4970 #1729 but no workaround or merged fix worked.

Steps to reproduce

Tell us about your environment:

• Puppeteer version: 1.20
• Platform / OS version: tested on Mac OS 10.13.6 and Last Amazon Linux 2 in Docker
• URLs (if applicable): http://www.faalkaart.nl
• Node.js version: v12.4.0

What steps will reproduce the problem?

Please include code that reproduces the issue.

Run this code:

const puppeteer = require('puppeteer');
const url = 'http://www.faalkaart.nl';
// const url = 'https://basisbeveiliging.nl/'; // with this it works
(async () => {
    const browser = await puppeteer.launch();
    const page = await browser.newPage();
    // The following shows that redirection are followed:
    // await page.setRequestInterception(true);
    // page.on('request', r => { console.log(r._url); r.continue() });
    const response = await page.goto(url, {
        timeout: 15000,
        waitUntil: ['domcontentloaded', 'networkidle0']
    });
    // await page.waitFor(5000); // If we intercept request and wait we can see that the page is loaded but the context had been lost since response is null
    if (response) {
        console.log('Response is OK');
    } else {
        console.log('Response is null');
    } 
    await browser.close();
})();

What is the expected result?

Response is OK

What happens instead?

Response is null

Some ideas about the cause

Intercepting request I was able to see that redirection chain is

1. http://www.faalkaart.nl/
2. http://faalkaart.nl/
3. https://faalkaart.nl/ <— domcontentloaded is triggered after this one
4. https://basisbeveiliging.nl/ <— networkidle0 is triggered after this one

[stale[bot]]

We’re marking this issue as unconfirmed because it has not had recent activity and we weren’t able to confirm it yet. It will be closed if no further activity occurs within the next 30 days.

[stale[bot]]

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!