Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

Question

Broken Windows' New Releases?

Nov 24, 2011 4:21AM PST

Hi!

http://download.cnet.com/new-windows-software/ shows "Whoops! You broke the Internet!





No, really, it looks like you clicked on a borked link or something.You could try searching for what you want here:










Or go to the CNET homepage.Or speaking of 404, you could always check out CNET's Internet snark machine, The 404 Podcast."

Where is it now? Sad Thank you in advance. Happy

Discussion is locked

- Collapse -
Answer
Re: broken link
Nov 24, 2011 4:26AM PST

I've alerted the forum administrator, so he can warn the download.com-team about this error. Thanks for telling.

Kees

- Collapse -
Answer
Seems to be working now
Nov 24, 2011 7:23PM PST

Clicking that link you gave seems to be working now, for me at least.

Looks like they got Kees' message. Happy

Mark

- Collapse -
Yes, but...
Nov 24, 2011 10:32PM PST
- Collapse -
(NT) That link works fine for me.
Nov 25, 2011 2:35AM PST
- Collapse -
I'm gettng a page 6 fail
Nov 25, 2011 3:42AM PST

All pages 1-5 and 7-9 work for me, I didn't go further.

Page 5 works here; http://download.cnet.com/windows/3151-20_4-0-5.html?tag=page

But page 6 failed for me.

This is an ever changing list as new products are added. So may be your page 5 is now my page 6.

I will alert this again as it looks like a particular page listing is faulty.

Mark

- Collapse -
...
Nov 25, 2011 5:14AM PST

Yeah, it looks like there is a problem on that specific page that is getting older. I hope I didn't miss anything important. Sad

- Collapse -
I tried it and it's working now
Nov 28, 2011 1:01AM PST

I paged through 1-11 and they all loaded for me. Possible glitch on the results for a particular product on that page that day?

Regardless if you see this again please let me know about it and I will let the Download.com team know about it.

Thanks and sorry about the troubles.

-Lee

- Collapse -
I saw it this morning...
Nov 28, 2011 1:26AM PST

It was on page 9 at the time, 404ing consistently. But by the time I finished writing an alert on it, the page was working again - and no problems in the hours since.

Cheers for the auto-fix!
John

- Collapse -
Typical
Nov 28, 2011 4:41AM PST

You only have to 'look' at something and it's fixed!

Still, better than you breaking things all the time, huh? Devil

Mark

- Collapse -
I think I scared it...
Nov 28, 2011 6:29AM PST

I've broken the forums so much, all I have to do is glare at 'em and they shape up in fear of what I may do next. Devil

John

- Collapse -
(NT) LOL
Nov 28, 2011 8:08PM PST
- Collapse -
Answer
I'll let the Download.com team know...
Dec 7, 2011 1:39AM PST

that this is still an intermittent issue.

I think when Download.com bumped the results pages up from 15 to 50, the request to retrieve more titles per page occasionally will take longer than usual and eventually causing the page to fail.

Thanks for reporting this all.

-Lee

- Collapse -
UPDATE
Dec 13, 2011 8:46AM PST

Hey all,

The Download.com team investigated the issue, and it looks like my hunch was right from above. Because each page lists so many download titles, occasional the page will fail if all the data doesn't get loaded on to the page quickly enough.

As stated from the engineer this shouldn't happen very often. However, if it does, please let me know about it.

Also if this does so happen to you, when you refresh your browser page, does it resolve the issue for you?

Thanks!
-Lee

- Collapse -
...
Dec 13, 2011 11:10AM PST

Lee, when it happened on 11/24/2011, I did reload/refresh but got that error. Oh well.

- Collapse -
Likewise here...
Dec 13, 2011 9:15PM PST

I refreshed a dozen times and kept getting the PNF. But when I checked it one last time after writing an alert, it was consistently working. I assume the failure was cached, causing the consistent PNF for a brief time rather than being more sporadic.

John