Tags: httpd, humor, innuendo, internet, lingerie, photos, sex, women
Every time your web browser sends a request to a webserver (an HTTPD), the browser returns a code, along with some content.
Does everyone remember all of the HTTPD Codes? I’m a dork, so I do…
|Successful Client Requests|
|Client Request Redirected|
|Client Request Errors|
|402||Payment Required (not used yet)|
|405||Method Not Allowed|
|406||Not Acceptable (encoding)|
|407||Proxy Authentication Required|
|408||Request Timed Out|
|411||Content Length Required|
|413||Request Entity Too Long|
|414||Request URI Too Long|
|415||Unsupported Media Type|
|505||HTTP Version Not Supported|
So Amanda from Fashionista TV was visiting today, and in browsing her site, I ran across her blog post about HTTPanties for sale from ThinkGeek…
Given the above list, I can find plenty of more clever variations. These messages could be extremely helpful prior to coredumping your RAM…. Really, you never want to have an infected Hard Drive, do you?
How about “412 Precondition Failed” and “503 Service Unavailable” for the frigid?
Perhaps sex workers could put “402 Payment Required” to good use.
“303 See Other” for swinging married women who get around.
“407 Proxy Authentication Required” is a shoe-in for bisexuals, and “409 Conflicting Request” works great if they’re still a bit confused…
Lesbian consumers also have a number of options, but the best has to be “415 Unsupported Media Type.”
Of course, “502 Bad Gateway” across the ass is usually a given… But “300 Multiple Choices” would work well for hermaphrodites, porn stars, and the exceptionally kinky…
And I can certainly think of a few women who should be wearing “500 Internal Error” … 😉