Reactos web pages go to bluescreen?

[LMH1]

Its a long time, that i used reactos web pages.

But if i go to: http://www.reactos.org/no/about_roadmap.html

Get i bluescreen?
[ external image ]

Why? Not on my computer, but as webpage?

Is it ROS server or a new error message?

[zefklop]

It's a funny way to tell you that you tried to get a non-existing page.

[SuperDog]

That's just pure HTML - nothing to worry about.

[jgwright]

So, try to fetch a page that doesn't exist and it doesn't return a 404 but a status 200 avec 'blue screen' with suggestion to restart the browser. It's neither clever nor funny, IMO.

[Z98]

Page exists. It's just been replaced with a HTML BSOD. Since the page exists, there is no error code to return.

[jgwright]

Are you sure? I delete characters from the url and they all give me 200 with 'blue screen' as well. They all exist as well right? Repeat: not clever, not funny.

[SuperDog]

I must agree with jgwright in this regard.

[EmuandCo]

It stays as long as the website maintainer likes it. Btw, our devs like it too.

[ThePhysicist]

If you see this screen it should be obvious, that it's an imitated Windows BSOD.
If you don't find it funny, that's ok, it's a matter of taste probably and not a requirement for the page.
If you don't find it clever, it's ok, too. Although the page is actually pretty clever, as it's displaying useful info.
If you have you have a problem with the suggestion to restart your browser, then don't do it.
Although doing it won't hurt you and might actually help in case your browser fucked up some cookies or something.

Regards,
Timo

[jgwright]

It's disappointing that two 'developers' seem to fail to get the main point. It's all about *standards*. HTTP headers are important. They're well defined, painstakingly so, lots of people follow them, necessarily so.

A lot happens between a the script on a webserver being uploaded and a page appearing on my browser. Perhaps we all know about caching tools, these appear all over the network - from right next to the server to being built into the browser itself. There are various browser helper tools. More importantly, online services (Google) will look at headers, in their (increasingly futile) attempt to de-spam the neighbourhood. Third-party tools - think link checkers - will help in the effort.

Last year I attempted to weed out dead or spammy urls from a 43MB dump. The tricks that the bad guys used to stop their urls being weeded out I found interesting. When I found the 'good guys' up to daft tricks as well I was less than humoured.

Keeping up with the standards is about being good neighbours.

Is the ReactOS project similarly 'funny' with IP headers? It would indeed be a jolly jape to have lots of easter eggs popping up with our IP traffic, and on these forums there's palpable anticipation of the next release. April 1st maybe?

[DangerGround]

Yes you're right, the sites reported wrong HTML status, now they should report the correct one. Thanks for reporting.

[RaptorEmperor]

I think the BSOD on here is hilarious. It's as good as about:robots in Firefox.

[vicmarcal]

I love the error page

[jgwright]

Excellent. A BSoD mockup is a lot funnier when it's returning the correct status!

[EmuandCo]

jgwright, sry I thought you just were against the erros screen at all. I overread the wrong status. NVM k?