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

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.

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

  • C# Advent Calendar 2019 – Refactoring RestSharp Sample Tests to Make Them More Maintainable
  • Being Prescribed Something I’m Allergic To aka Software Doesn’t Work
  • Choosing the Winner for the Pro Ministry of Testing Dojo Membership!
  • Ministry of Testing Dojo Membership – #PayItForward
  • Looking back on 2018, looking forward to 2019

Categories

  • Career and Leadership
  • Coding Stuff
  • Conferences and UG Meetings
  • Gluten Free
  • HTTP Status Coops
  • Personal Stuff
  • Professional Stuff
  • REST API Testing
  • Testing
  • Uncategorized

Upcoming Events

There are no upcoming events at this time.

© 2018 g33klady.com / Hilary Weaver-Robb. All rights reserved.