Going to a non existing node loads a full list of nodes: cause unnecessary server load with crawlers

So, is this a known bug ?

Since this is fixed on drupal.org, can we know the fix to apply on our own installations ?

Thanks,
Brakkar

Ok, so this bug was fixed on 5.2 drupal release. It affected drupal.org and my site.
But a part of the problem still needs to be fixed:

As you can read, this bug caused the load of unwanted results when going to a non existing node.

It created an ugly paginations of hundreds of unwanted pages. The problem is that now, these pages are still in search engines and search engines are visiting them thus it still create unwanted load:

When I load a page like http://www.mysite.com/taxonomy/term/17...?page=10, it will display a page not found message, but just bellow it, the entire list of the nodes of my site, badly paginated as in the line above, creating unwanted load on the server and unwanted pages in the search engines.

I don't know if this is related to drupal core or views specifically, but there is something wrong here.

Just a note: when going to the bad url with the 3 dots, it seems the error page isn't standard not found page, but the page I created once and specified in the error-reporting setting. I had then removed the specification of the url from there, still, it seems the system loads this page when going to the curious url. When going to other non existing page, it loads the standard, unspecified "page not found" message. Might be a clue to the bug.

Cordially,
Brakkar