Skip to content
g33klady
  • Home
  • Blog
  • Talks
  • HTTP Status Coops
g33klady

HTTP Status Coop – 400 Bad Request

October 23, 2017 by Hilary

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!

Hilary
Hilary

I’m Hilary Weaver-Robb, also known as g33klady on the Internets. I’m a Senior Quality Engineer working remotely near Detroit, I tweet a lot (@g33klady), and swear a lot, too.

Post navigation

Previous Post:

HTTP Status Coop – 307 Temporary Redirect

Next Post:

HTTP Status Coop – 403 Forbidden

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • 2022 Year In Review and 2023 Goals
  • Diversifying Heuristics with Social Media part 2
  • Diversifying Heuristics with Social Media
  • A Birthday Surprise That Didn’t Go To Plan (but was Still Incredible!)
  • 2020 and 2021 Years in Review, and Looking Forward to 2022

Categories

  • Career and Leadership
  • Coding Stuff
  • Conferences and UG Meetings
  • Gluten Free
  • HTTP Status Coops
  • Personal Stuff
  • Professional Stuff
  • REST API Testing
  • Testing
  • Uncategorized
© 2018 g33klady.com / Hilary Weaver-Robb. All rights reserved.