[Bug]: Redirect stops before the final destination that has an error Name Not Resolved about puppeteer HOT 4 CLOSED

This issue has an outdated Puppeteer version: 21.10.0. Please verify your issue on the latest 22.7.1 version. Then update the form accordingly.

Analyzer run

from puppeteer.

There is no expectation from Puppeteer here to return the last response URL, we return the one the user tried to navigate to.
You could work around this by:

let lastNavigationRequest;
page.on('request', req =>{
    //...
    if (req.isNavigationRequest() && req.frame() === page.mainFrame()) {
      lastNavigationRequest = req;
    }
    // Prevent the error form throwing
    await page.goto(...).catch(() => {});
    console.log(lastNavigationRequest.url());
})

Currently Puppeteer does not provide a means to get the request from a failed navigation directly from the page.goto() command.

from puppeteer.

@Lightning00Blade Thanks for your reply however I think there was a misunderstood about the nature of the bug i'm referring to.

For the error : Name Not Resolved , i don't want to get rid of it, in fact, i want to know where exactly in URL's chain it happened, which logically MUST be in the last url that appears. But when i catch the error while navigation, it shows that the error of Name Not Resolved has appeared in the url before final destination ( which is wrong )

from puppeteer.

How puppeteer works is that is sends a command and it fails due to request being canceled,
in such cases we don't try to find the HTTP response associated with the error as we get it from the command.
There is a feature request to support getting the last response from the page #11555
But this is already achievable through page.on('request') with example above given.

from puppeteer.