Ошибка 404 страшилка

БОЛЬШЕ ИСТОРИЙ

This fantastically good pasta was authored by theidealist!

Huge aspirations are behind this work, penned in a burst of inspiration. Perhaps this notice is a little exaggerated though…

Intro

Hello. I am th3_1NFIni7e. This is my story.

Have you heard of Entity 303? People always talk of him trivially, jokingly. Some things have that strange habit: of seeming silly. Until they strike; until they actually happen to you.

It all began with fr13ndz. That was the name of a server I created, a server I shared with my friends. It was a Creative server, and I was the admin.

I was the admin. Not any more. Now, I am banned. So are my friends. It is ruined.

And why?

How it all began

It was a friendly server. We were working on many fun projects. But then, one day, another player appeared, out of nowhere. I had never authorised him.

His name was ERROR_404.

What an interesting name, I thought to myself. At first, I was going to just have him banned immediately, but then I decided to /tp to him, to see what he was doing. Maybe he wouldn’t be too bad.

So I typed it in: /tp @p ERROR_404. And without success. Up came an error message. But it was unlike any such thing I had ever seen.

Error 404: Player "ERROR_404" not found.

Since when did Minecraft put the error number in front of an error message? I tried again, with the same result. Wondering if the ‘player’ was a glitch, I got on with my own builds.

The second happening

But it was not long before another strange occurrence. As I was running towards a build over the horizon, one of the chunks on its corner turned black. Pitch-black.

Then, Minecraft froze. My cursor separated from the crosshairs. ‘Not Responding’ appeared on the window’s heading. A second later, an error window popped up.

It was headed ‘Error 404’. It read:

Error 404: Chunk not found - Unable to load
Players currently in chunk:  - ERROR_404

At this point, I knew for certain that something was wrong.

I clicked ‘OK’. Minecraft crashed. When I reopened it, I found that I was banned — from my own server.

Later

Later, I was able to reenter. When I did, I found to my intense dismay that the entire chunk had been cleared — to the ground. Tons of work, evaporated into thin air. Even more annoyingly, two other corners had gone black.

«Please. Not again.» I whispered, fervently.

But it was again, and the computer went through the whole rigmarole once more. This time, though, I kept a close eye on my server, and joined as soon as it reappeared. Immediately, I tentatively peeked at my great build, anticipating terrible evil.

And gasped in horror.

Flames were licking all over my palace, throwing months of work out the window, spreading ever closer to —

A huge pillar of TNT.

«No.» I muttered in shock. I sprinted, full pelt, towards it, hoping to stop the fire somehow. But I was arrested in mid-flight by a wall of invisible bedrock.

I couldn’t destroy it for some reason. I could only watch, helpless, as my palace exploded into oblivion.

But as I watched, I spotted a small, dark figure in the corner of the screen, leaping away from the flames. Instinctively I rushed after it, in pursuit, wondering if it was by any chance — ERROR_404?

The confrontation

My instincts were proven correct. As I neared the figure, I caught sight of its gamertag. Unsurprisingly, it was ERROR_404.

My heart was all a-flutter. Butterflies had spawned into my stomach. I, at last, could contend with this menace!

I alighted next to him. He did nothing, so I opened my chat-box. This is how our talk went:

(ME) Why the destruction?

(ME) Why the errors?

(HIM) Why the happiness?

(ME) I have as much right as you to be happy.

(HIM) I have no right to be happy.

(ME) Why?

(HIM) The existence of this fiendish game.

Very interesting.

(ME) It is good.

(HIM) It hates me.

(ME) You hate it.

(HIM) Both correct.

(ME) Even if you bear a grudge against it,

(ME) Why take it out on me?

I knew the question ought to be asked.

(HIM) You play it.

And now for the biggie, I thought…

(ME) Who are you?

(HIM) Find it out.

(HIM) If you don't, within 3 Minecraft days,

(HIM) Then you will be banned.

What on earth?!!!

(ME) By what right??

(HIM) My right.

(HIM) The right of an admin.

Again, how?!

(ME) Of a hacker!

(HIM) And you'd better believe it!

(HIM) For you are powerless against it.

The search

I was terrified at that, I can tell you! Immediately I checked his status, and it was indeed OP. I tried to de-OP him, but yet again the message popped up, along with another one:

Error 404: Player "ERROR_404" not found.
Don't even try.

He seemed to have a weird niche between player and non-player.

I told my friends of this, and asked them to leave, in case they came to harm. But as soon as they left, they were mysteriously perma-banned. Not by me!

I would have to face ERROR_404 alone.

I put up a message on several forums, giving a synopsis of the occurrences, and asking who it could be. One was insta-deleted, and the others, when I looked for comments later, the page 404’d — quite fittingly. ERROR_404 must have wanted me to keep quiet about him.

And what else could I do?

I looked it up, but all I got were things about Error 404 on Google. No help.

But then I thought of a few things. I could back up my world, and recreate it into a different Realm. Besides, didn’t hackers often edit source codes? I could check them.

The end of the server

I already had backups from before this great evil arrived, so I entered the world — in what was fated to be the last time. It was already almost midday on the third day. Only five minutes left; but a lot can be done in five minutes.

I left and opened the source codes. Nothing unusual. I looked through it for several minutes. And I was rechecking it when —

Behold!

Right before my eyes, one line of code began to change, letter by letter, as if it was being edited at the same time. I reread it, and my blood ran cold.

34852-AFCQTRW-TIMEUP-MAKEAWISH-404/303-MS-9362807

Make A Wish. 303. Those fiendish phrases, the ones I never bothered to care about. And now it had happened to me, myself.

At long last, I knew the culprit. But my time was up.

Alas, it was too late. Much, much too late…

The conclusion

I am crazy_steve. I am the one who spotted the 404 message as it was put up — although it 404’d right after. I am the only one who knew its meaning.

I had a friend, similarly named crazy_alex_2, who once had a nerve-wracking 303 encounter. She gathered clues, accidentally dropped by 303, suggesting that he was going to try a new tactic; being a player, yet partially not, and so evading any harmful commands while terrorising the game.

When I saw the 404 message, I knew this was it.

I gave him a message, telling my e-mail address and asking him to e-mail me, and ask questions later. Once he had done so, I told him why; it was to keep away from 404.

He e-mailed me with lots more info. He told me of the end of the server, and also how the back-ups had been corrupted. And I told him of my friend’s encounter.

We put it up here on the Creepypasta Wiki, where 404/303 would not look for it, and to tell the world of it.

Please bring publicity. Everyone must know — everyone must be warned of this terrifying new tactic, devised by Entity 303.

This fantastically good pasta was authored by theidealist!

Huge aspirations are behind this work, penned in a burst of inspiration. Perhaps this notice is a little exaggerated though…

Intro

Hello. I am th3_1NFIni7e. This is my story.

Have you heard of Entity 303? People always talk of him trivially, jokingly. Some things have that strange habit: of seeming silly. Until they strike; until they actually happen to you.

It all began with fr13ndz. That was the name of a server I created, a server I shared with my friends. It was a Creative server, and I was the admin.

I was the admin. Not any more. Now, I am banned. So are my friends. It is ruined.

And why?

How it all began

It was a friendly server. We were working on many fun projects. But then, one day, another player appeared, out of nowhere. I had never authorised him.

His name was ERROR_404.

What an interesting name, I thought to myself. At first, I was going to just have him banned immediately, but then I decided to /tp to him, to see what he was doing. Maybe he wouldn’t be too bad.

So I typed it in: /tp @p ERROR_404. And without success. Up came an error message. But it was unlike any such thing I had ever seen.

Error 404: Player "ERROR_404" not found.

Since when did Minecraft put the error number in front of an error message? I tried again, with the same result. Wondering if the ‘player’ was a glitch, I got on with my own builds.

The second happening

But it was not long before another strange occurrence. As I was running towards a build over the horizon, one of the chunks on its corner turned black. Pitch-black.

Then, Minecraft froze. My cursor separated from the crosshairs. ‘Not Responding’ appeared on the window’s heading. A second later, an error window popped up.

It was headed ‘Error 404’. It read:

Error 404: Chunk not found - Unable to load
Players currently in chunk:  - ERROR_404

At this point, I knew for certain that something was wrong.

I clicked ‘OK’. Minecraft crashed. When I reopened it, I found that I was banned — from my own server.

Later

Later, I was able to reenter. When I did, I found to my intense dismay that the entire chunk had been cleared — to the ground. Tons of work, evaporated into thin air. Even more annoyingly, two other corners had gone black.

«Please. Not again.» I whispered, fervently.

But it was again, and the computer went through the whole rigmarole once more. This time, though, I kept a close eye on my server, and joined as soon as it reappeared. Immediately, I tentatively peeked at my great build, anticipating terrible evil.

And gasped in horror.

Flames were licking all over my palace, throwing months of work out the window, spreading ever closer to —

A huge pillar of TNT.

«No.» I muttered in shock. I sprinted, full pelt, towards it, hoping to stop the fire somehow. But I was arrested in mid-flight by a wall of invisible bedrock.

I couldn’t destroy it for some reason. I could only watch, helpless, as my palace exploded into oblivion.

But as I watched, I spotted a small, dark figure in the corner of the screen, leaping away from the flames. Instinctively I rushed after it, in pursuit, wondering if it was by any chance — ERROR_404?

The confrontation

My instincts were proven correct. As I neared the figure, I caught sight of its gamertag. Unsurprisingly, it was ERROR_404.

My heart was all a-flutter. Butterflies had spawned into my stomach. I, at last, could contend with this menace!

I alighted next to him. He did nothing, so I opened my chat-box. This is how our talk went:

(ME) Why the destruction?

(ME) Why the errors?

(HIM) Why the happiness?

(ME) I have as much right as you to be happy.

(HIM) I have no right to be happy.

(ME) Why?

(HIM) The existence of this fiendish game.

Very interesting.

(ME) It is good.

(HIM) It hates me.

(ME) You hate it.

(HIM) Both correct.

(ME) Even if you bear a grudge against it,

(ME) Why take it out on me?

I knew the question ought to be asked.

(HIM) You play it.

And now for the biggie, I thought…

(ME) Who are you?

(HIM) Find it out.

(HIM) If you don't, within 3 Minecraft days,

(HIM) Then you will be banned.

What on earth?!!!

(ME) By what right??

(HIM) My right.

(HIM) The right of an admin.

Again, how?!

(ME) Of a hacker!

(HIM) And you'd better believe it!

(HIM) For you are powerless against it.

The search

I was terrified at that, I can tell you! Immediately I checked his status, and it was indeed OP. I tried to de-OP him, but yet again the message popped up, along with another one:

Error 404: Player "ERROR_404" not found.
Don't even try.

He seemed to have a weird niche between player and non-player.

I told my friends of this, and asked them to leave, in case they came to harm. But as soon as they left, they were mysteriously perma-banned. Not by me!

I would have to face ERROR_404 alone.

I put up a message on several forums, giving a synopsis of the occurrences, and asking who it could be. One was insta-deleted, and the others, when I looked for comments later, the page 404’d — quite fittingly. ERROR_404 must have wanted me to keep quiet about him.

And what else could I do?

I looked it up, but all I got were things about Error 404 on Google. No help.

But then I thought of a few things. I could back up my world, and recreate it into a different Realm. Besides, didn’t hackers often edit source codes? I could check them.

The end of the server

I already had backups from before this great evil arrived, so I entered the world — in what was fated to be the last time. It was already almost midday on the third day. Only five minutes left; but a lot can be done in five minutes.

I left and opened the source codes. Nothing unusual. I looked through it for several minutes. And I was rechecking it when —

Behold!

Right before my eyes, one line of code began to change, letter by letter, as if it was being edited at the same time. I reread it, and my blood ran cold.

34852-AFCQTRW-TIMEUP-MAKEAWISH-404/303-MS-9362807

Make A Wish. 303. Those fiendish phrases, the ones I never bothered to care about. And now it had happened to me, myself.

At long last, I knew the culprit. But my time was up.

Alas, it was too late. Much, much too late…

The conclusion

I am crazy_steve. I am the one who spotted the 404 message as it was put up — although it 404’d right after. I am the only one who knew its meaning.

I had a friend, similarly named crazy_alex_2, who once had a nerve-wracking 303 encounter. She gathered clues, accidentally dropped by 303, suggesting that he was going to try a new tactic; being a player, yet partially not, and so evading any harmful commands while terrorising the game.

When I saw the 404 message, I knew this was it.

I gave him a message, telling my e-mail address and asking him to e-mail me, and ask questions later. Once he had done so, I told him why; it was to keep away from 404.

He e-mailed me with lots more info. He told me of the end of the server, and also how the back-ups had been corrupted. And I told him of my friend’s encounter.

We put it up here on the Creepypasta Wiki, where 404/303 would not look for it, and to tell the world of it.

Please bring publicity. Everyone must know — everyone must be warned of this terrifying new tactic, devised by Entity 303.

Ошибка 404 Page Not Found преследует экраны компьютеров по всему миру на протяжении десятилетий. И хотя многие пользователи до сих пор не знают, почему она возникает, «последняя страница Интернета» за последние тридцать лет появлялась так часто, что проложила себе путь в поп-культуру как городская легенда.

Мы не осознаём этого, но подобная ошибка встречается довольно часто, поскольку большинство сайтов каждый день сталкиваются с новыми неработающими ссылками. Более того, веб-страницы, созданные до 2005 года, постоянно «умирают». Следовательно, мы можем только гадать, сколько надгробий с надписью 404 Page Not Found существует на онлайн-кладбище.

Сегодня 404 является мощным символом, который используют во всём мире для освещения чего-либо неизвестного.

Что такое 404 Page Not Found?

Мы все с ней сталкивались, но как возникает эта ошибка? 404 – это код состояния HTTP. Когда пользователь посещает веб-страницу, устройство запрашивает данные с сервера с помощью HTTP — протокола прикладного уровня передачи данных.

После этого колёса и шестерёнки всемирной паутины начинают двигаться, и мы осознаём, что всё в Интернете связано с обменом данными quid pro quo (одна передача зависит от другой). Перед тем как отобразить страницу, веб-сервер отправляет HTTP-заголовок с кодом состояния, и наш браузер отвечает взаимностью, отправляя свои заголовки. Если всё нормально, статус обмена данными считывается нормально:

«200 ОК».

«Запрос выполнен успешно».

Мы не видим этого, поскольку сервер отправляет содержимое страницы. Код выдаёт, если происходит ошибка.

«404 Not Found».

Такое случается, когда запрашиваемая страница больше не существует. Эта ошибка довольно распространена и может возникнуть на любом веб-сайте.

Развенчание мифа о комнате 404

В период с 1981 по 1992 год, работая в ЦЕРНе, изобретатель всемирной паутины Тим Бернерс-Ли и его помощник Роберт Кайо создали новую систему просмотра и распространения информации на основе гипертекста. Им приходилось отвечать на различные запросы, выделяя файлы и передавая их по сети, и делали они это вручную.

Вскоре они стали настолько перегруженными, что не могли отвечать на все запросы, отправляемые через сеть. Пользователи, которых стало слишком много, вводили неправильные данные и в конечном итоге отправляли не те названия файлов.

Поскольку одни и те же проблемы возникали постоянно, учёные обновили систему, придумав сообщение для тех, кто отправлял запросы с неправильными названиями файлов. Оно выглядело следующим образом:

«Room 404: file not found».

Сообщение стало популярным. В 1992 году Консорциум Всемирной паутины ввёл коды состояния HTTP, которые были разработаны ещё в 1990 году.

Тим и Роберт работали вместе в офисе на четвёртом этаже здания. Там же, в комнате под номером 404, располагалась центральная база данных всемирной паутины с первыми веб-серверами.

«Первый веб-сайт в ЦЕРНе – и в мире – был посвящён самому проекту всемирной паутины (World Wide Web) и размещался на компьютере NeXT Бернерса-Ли. В 2013 году ЦЕРН запустил проект по восстановлению первого в истории веб-сайта: info.cern.ch».

Роберт Кайо развенчал миф о том, что ошибка 404 была названа в честь серверной комнаты в ЦЕРНе. На четвёртом этаже не было комнаты с номером 404.

Как ни странно, в здании «4» нет комнаты «04», офисы начинаются с 410-го — не спрашивайте, почему. Извините, что разочаровываем вас, но в ЦЕРНе нет комнаты 404 — её просто не существует, и уж точно не она была «местом, где зародилась паутина».

Роберт Кайо подтвердил это во время интервью: «Цифра 404 никогда не была связана с какой-либо комнатой или физическим местоположением в ЦЕРНе. Это самый настоящий миф».

Когда его спросили об одержимости людей термином 404, Кайо ответил: «Вероятно, это связано с иррациональностью, отрицанием очевидного и ухода от реальности, что весьма характерно для людей».

Разгадка тайны 404

Таким образом, ошибка 404 стала Интернет-загадкой и нигилистическим парадоксом. Тем не менее, скорее случайно, чем преднамеренно, нам, возможно, удалось найти ответ. Дело в том, что любители городских легенд и разрушители мифов искали разгадку не в той комнате в ЦЕРНе.

Рейсы 404

Код 404 появился ещё тогда, когда Интернет только зарождался. Тим Бернерс-Ли изобрёл всемирную паутину (WWW) в 1989 году, и именно в тот год произошла первая трагедия с участием самолёта, выполнявшего рейс 404.

Рейс 404 Pakistan International Airlines

Рейс PK404 исчез почти сразу же после взлёта 25 августа 1989 года. Самолёт Fokker F27 Friendship поднялся в небо в Гилгите (Пакистан) в 7:35, он держал курс на столицу Исламабад.

В 7:40 пилоты вышли на связь. Затем самолёт исчез с радаров. Эксперты полагают, что он разбился в Гималаях, однако до сих пор не было обнаружено никаких обломков. Рейс 404 исчез бесследно.

Можете себе представить, сколько раз Тим Бернерс-Ли и Роберт Кайо слышали об этом в новостях. У них могла неосознанно отложиться в памяти фраза «404-й не найден».

Рейс 404 авиакомпании Alitalia

Рейс 404 авиакомпании Alitalia был международным пассажирским рейсом, который 14 ноября 1990 года направлялся из аэропорта Линате в Милане, Италия, в аэропорт Цюриха в Швейцарии, и потерпел крушение. Самолёт Douglas DC-9–32 компании Alitali, приближаясь к аэропорту Цюриха, упал в лесах Вайаха, убив всех 46 человек, находившихся на борту.

Между Вайахом и местом рождения Интернета в ЦЕРНЕ всего около 240 километров. Новостные каналы, вероятно, связали трагедию с рейсом PK404. Следовательно, мы можем предположить, что цифра 404 снова засела в подсознании каждого.

Заключение

Оглядываясь на историю Интернета, мы видим, что сочетание неблагоприятных обстоятельств, известных как «идеальный шторм», породило ошибку 404. Удивительно, почему до сих пор никто не соединил следующие точки:

* Август 1989 года – рейс PK404 исчезает вскоре после взлёта.

* Октябрь 1990 года – Тим Бернерс-Ли начинает писать код для клиентской программы, браузера/редактора, который он называет World Wide Web, на своём новом компьютере NeXT.

* Ноябрь 1990 года – рейс Alitalia 404 терпит крушение в Швейцарии.

* Декабрь 1990 года – появляется первый веб-сайт, nxoc01.cern.ch.

Тим Бернерс-Ли и Роберт Кайо молчат об истинном происхождении сообщения «404 not found». Однако они могут даже не подозревать о подсознательных нюансах «404». Следовательно, ошибка продолжит пугать пользователей сети как «тупиковая страница Интернета».