HTTP Status Coop – 400 Bad Request

Oct 23

Posted by

Seventh in the HTTP Status Coop series is 400 Bad Request!

400BadRequest_img

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!

Advertisements

Posted on October 23, 2017, in HTTP Status Coops. Bookmark the permalink. Leave a comment.

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

w
Cancel

Connecting to %s

%d bloggers like this: