posts tagged with the keyword ‘server’

2011.02.17

tapps posted something to Twitter, I replied and turned it into a joke, and it went a little crazy from there with some help from janiukjf and chernowa … Here’s the transaction. (I’ve saved it here since at some point it may will become unavailable on Twitter.)

Server Errors

As long as we’re on the subject, I thought I’d expand on the whole “Server Error” joke and attempt to come up with a restaurant/food/server joke for every HTTP code.

Informational 1xx – This is when your server introduces themselves to you.

100 Continue – This happens if you interrupt the server before they tell you the specials.

101 Switching Protocols – If the server realizes you are being difficult, stupid, or drunk, they may change the way they talk to you.

Successful 2xx – Hooray! You’ve managed to interact successfully with your server.

200 OK – Server is OK, hasn’t screwed anything up yet.

201 Created – You’ve decided what you wanted to order, and told the server.

202 Accepted – The server has accepted your order.

203 Non-Authoritative Information – If someone tells you that the burgers are good, find out who they heard it from. (Make sure it wasn’t Yelp.)

204 No Content – This is what happens when you are not content with your food.

205 Reset Content – This is what happens when you send the food back.

206 Partial Content – This is what happens when the server forgot something you ordered.

Redirection 3xx – This is what happens when the server starts coming towards your table, but turns and goes the other direction.

300 Multiple Choices – Typically, this will happen when they list the desserts… Choosing is quite difficult!

301 Moved Permanently – Occasionally you may want to move to another table, perhaps by the window, or the fireplace.

302 Found – Hooray! You thought you lost your server, but you found them.

303 See Other – This is what happens when you try to order from an employee who is not your server.

304 Not Modified – This is what happens when you send it back and then they return it without doing anything to it.

305 Use Proxy – This is when you have someone order for you, you know, if you have to go to the bathroom or something.

307 Temporary Redirect – This is when you make everyone else order before you because you haven’t decided yet.

Client Error 4xx – Oops! You’re the client, you’ve done something wrong… You probably pissed off your server.

400 Bad Request – Again, you screwed up. Did you try ordering a steak at a vegan restaurant?

401 Unauthorized – This is what happens if someone tries to order for you but you stop them.

402 Payment Required – Most restaurants rely on this one.

403 Forbidden – Asking your server for his/her phone number.

404 Not Found – Server is missing… probably on break.

405 Method Not Allowed – This is what happens if you try to order the kids meal when you’re a full grown adult.

406 Not Acceptable – If you get “grabby” with your server, well,that’s just not acceptable.

407 Proxy Authentication Required – If someone orders for you, and the server asks if it’s OK that they ordered for you…

408 Request Timeout – Server asks ” Do you need a little more time to decide?” Then leaves. (This is usually followed by a 404 error.)

409 Conflict – You really want the lobster, but you also really want the streak. Can’t have both!

410 Gone – Server has quit. Probably on a bus half way home already.

411 Length Required – This one is typically only used when ordering subs.

412 Precondition Failed – You may have ordered alcohol, but you’re not 21 yet. #fail

413 Request Entity Too Large – You know that 72 ounce steak that they give you, and if you eat the whole thing your meal is free? Don’t do it! It’s too large.

414 Request-URI Too Long – Occasionally someone will try to order everything on the menu…

415 Unsupported Media Type – Don’t try ordering your meal by singing.

416 Requested Range Not Satisfiable – You want free range beef. They don’t have it.

417 Expectation Failed – Your meal sucked.

Server Error 5xx – Server screwed up. It happens. (Go tell Yelp.)

500 Internal Server Error – Occasionally your server will be having emotional problems. Perhaps he (or she) is in love with two people at the same time…

501 Not Implemented – Not everything comes deep-fried and/or covered in cheese.

502 Bad Gateway – Typically an error between the server and the kitchen.

503 Service Unavailable – Server is not serving. See 404 and 410.

504 Gateway Timeout – This happens when the server gets too busy to relay your order to the kitchen.

505 HTTP Version Not Supported – Usually this only happens with older browsers. (Senior citizens who don’t know what to order. Or where they are. Or what year it is.)

Whew! Never let it be that I don’t know when to quit… because really, I don’t. END OF FILE

2007.04.07

I’ve written quite a bit about the Linksys NSLU2 we’ve been using at the office, and the problems we’ve have with it. (Linksys NSLU2 Update, Linksys NSLU2 versus ????) Overall it’s been a nice device for what it does, and for the price (about $80) but we’ve outgrown it, and we’re looking for a better solution.

I think that better solution is just going to be a server. (Going back to Small Business – Server & Backup I guess.) We should be able to solve most of the problems we had with the NSLU2 by using an old G4 PowerMac. The Mac should be faster than the NSLU2, and should not have any of the permission problems we’ve experienced. We’ll also be able to just deal with AFP instead of SMB since we’re a Mac-shop.

(I still think the NSLU2 is a good device for what it is, and for a home network would probably work well. Though reading up on FreeNAS it looks like a cool solution, and something I may try to play with in the future.)

The Mac will also allow us to do a few more things, like run the internal wiki, and possibly handle the office calendaring needs. What I really look forward to is automating our Amazon S3 backups using a Mac file server.

Anyway, I’m sure I’ll keep posting updates on this as we go…

2007.04.02

We are still using the Linksys NSLU2 as our file server, and we still aren’t 100% happy with it. (See Small Business – Server & Backup and Linksys NSLU2 versus ???? for background.)

Some Macs in our office seem to be able to connect via browsing the network, while others require typing in the smb://192.168.0.xx address. At least one Mac seems to see it, and use it, but then not be able to use it, then when you try to dismount, and remount, it says it’s already there and requires some command line magic (or a reboot) to clean things up.

After a recent reboot of the NSLU2, we noticed a few days later the backups were not running anymore. Seems that after the reboot the 1st drive was recognized fine, but the 2nd was not. I was just about to reformat the 2nd drive but thought I should reboot one more time – that fixed it! The 2nd drive was recognized and I just had to re-setup the backup schedule.

I think if we continue to have issues, I may just take a weekend and install Unslung on it.

2005.09.30

NSLU2-Linux looks like a fun little project. The Linksys NSLU2 is a “Network Storage Link” which means you typically attach it to your network, add an external USB hard drive, and it’s a file/backup server for the computers on your home network.

Pick one up at Amazon for about $80, and while you’re there grab an 80 GB drive for under $100 and you can build a nice little (and quiet) server running Linux, and once you’re running Linux, well, you open up a whole new world of possibilities…

Some links:

Need more info? It’s all over the place, just search for NSLU2 linux.

(I have a whole nother post on the trends I’ve noticed in small, cheap, hackable devices. So stay tuned…)

|


buy the button:

Buy The Button