HTTP Status Coop – 400 Bad Request
Seventh in the HTTP Status Coop series is 400 Bad Request!
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).
via Wikipedia
Cooper does *not* like hats…
For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
I’m Hilary Weaver-Robb, also known as g33klady on the Internets. I’m an SQA Architect in Detroit, I tweet a lot (@g33klady), and swear a lot, too.