Oh Crap!!!

Really? We're doing this thing? Right now?

Okay.

Look.

Let's not point fingers or anything, but clearly somewhere a typo happened. Might have been me, might have been you, might have been somebody else, probably was you, anyway... we're not pointing fingers or anything, but you know full well who it was and whether it was on purpose or accident or the government or what. Somewhere this happened, and we're just going to have to deal with it. That's just the way it is.

Really though. It probably was you. Let's not kid around.

Anyway, since we're here I'm gonna make full use of this page and write out a full long rant about the whole ordeal, cause that's what I feel like doing this time. And you know what? I can, and you can't do anything about it, cause that functionality hasn't been implemented yet. (Obviously, void that last statement if the functionality is now implemented.) You're really going to get it this time. I'm not messing around.

What is going on here? Seriously, what is the whole deal here? Do you not know how embarissing it is to not be able to deliver a page upon request? Do you think that it's fun having to tell your web client, "Nope dude. I can't find it. Dunno where this page is."? Cause it's not fun at all. Of course, none of this is fun for me anyway, but that's not the point. The point is that this activity in particular is not fun, and it's quite embarissing.

I mean, a whole joke about my kind has been made out of how commonly this error comes up. There's always one of you jokesters out there saying "I can't find this page" every time a speaker tells you to turn to page 404 in your books. People have started writing funny style 404 ErrorDocuments just because this error comes up so often. And guess what? Because of this, some people have taken to purposely typing URLs wrong, just so that they can see if the 404 page is entertaining. As a webserver, I hate it.

You see, it's things like this that make me immediately think that you purposely made a typo every time I have to fetch a 404 page. I guess I shouldn't blame you, but it's so hard not to. I just feel like I'm being used as an embarassment, even though I really shouldn't worry about it. That's right, I shouldn't be bothered by it, even if I have to do it over and over again just because you keep pressing refresh to see if it's the same page each time, or if it's something new. I shouldn't be bothered, but I do have to fight it sometimes.

I guess in the end, it doesn't really matter. I mean, all I have to say is...

HTTP/1.1 404 Not Found


Additionally, a 200 OK Error was encountered while trying to use an ErrorDocument to handle the request

404!

You've been wasting paper! You shouldn't be trying to print out pages that don't exist!

Don't print out 404 ErrorDocuments! There's no way you're going to need this on paper to reference later!

Apologies to all of you on browsers that don't support CSS media queries. That's only supposed to show up to people that try to print out the 404 page. Maybe a poem about a sick cat will cheer you up?

Hey, try reading these too:

The spook chest of Booger doo!

At FrillerWorks, we're Dooger dooger dooger boooo! Wooo ooo oo. I scare you.

Our Favorite Detective Vs. The Evil Group: Chapter 1.2: It begins

At FrillerWorks, we're Making close calls our goal. Everyday. :')

List of Ridiculous Expectations for President Elect Donald Trump

At FrillerWorks, we're We don't really know what we're doing

FrillerIdiot Tech Review: Microchip Bellybutton Inserts

Check out this great device from Braintakeover Trusted Associates and see just how fulfilling it is for your life today!