
It is no secret that bad things sometimes happen to good web sites. When this happens on your web hosting account, it is often shown as a HTTP error. Each problem that could happen with a web site, has an HTTP error code associated with it, which is suppose to tell you what the problem is. The problem is that they are not really translated into something the general public can understand.
Have no fear though, because I am going to give you five of the most common HTTP errors and what they really mean.
500 Internal Server Error
This is your general purpose error message from the server say, “Hey… none of the other messages really fit here, so we are just going to tell you something screwed up, please try again!”. It could be coming up because the site in question is overloaded with requests, or it could be a system admin trip over the power cord.
404 Not Found
Hey, that isn’t there – so go away is the general message you should get when you see a 404 error code. Probably the most famous error code, if they were ranked by popularity. The requested resource could not be found but may be available again in the future… if your lucky.
403 Forbidden
The 403 error is telling you, that you really are not suppose to be there. It is kind of like the 401 error code, except this time you didn’t even have the chance to try to log in to view the files. You are just not allowed, go away, you are not suppose to be trying to look at that.
400 Bad Request
When you get this HTTP error, it usually means your browser access the page in the wrong way, or somehow your request to view the page was corrupted along the way. The signal got lost, confused and started looking for a magic leprechaun, and totally forget about your request to view that site.
401 Unauthorized
With this web page error code, you see it when you put in the wrong user name or password when trying to log into a protected area. For example, you were trying to log into that ex-girlfriends photo collection to see if she had deleted all the pictures of you. Since you got the 401 error, you’ll never be able to see she simple edited your face out and replaced it with a headshot of Bill, that vampire guy, from True Blood.
Have another HTTP error that has you stumped? Leave a comment, and perhaps we will do a round two of these geek to regular speak HTTP error translations.
How Should Web Hosts Adapt to the Social Web?
Posted on Aug 11, 2009 in All Posts, Articles, Commentary
A lot of the appeal of Facebook or Twitter is that you catch people in the buff. No, not that there are a lot of nudist on the social networks. What I mean is there is a lot of “raw” and “un-edited” thoughts out there. Of course, that isn’t to say you can’t organized your “raw” thoughts before you get them out there.
How should web hosts act on social networks? It is all about striking the right balance of many different things you want to get out into the public. Here are a few topic ideas.
Support Updates – Having a major problem that is effecting many customers? Rather than hiding under your desk and sucking your thumb, it might be better to get out there in the angry mob and let them know what is going on. For the most part 95% of the population out there will be ok with disaster, as long as they know what is going on. Just think how happy those people on the Titanic would have been, for example, if the ship had a better PR person. It is something to think about.
Plug Yourself and Market to All – If you have a good following of people requesting to be your friend, you need to make sure you strike a good balance between giving your current followers something they can use, and also give the searchers out there a reason to look into you. Half you marketing posts should be focused towards your base and the other half should be focused toward potential customers.
So there you have it, follow these steps and you will finally have something to do on that Twitter account or Facebook fan page you haven’t touched in a while.