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

HTTP Status Coop – 413 Request Entity Too Large

November 10, 2017 by Hilary

Twelfth in the HTTP Status Coop series is 413 Request Entity Too Large (or Payload Too Large)!

413RequestEntityTooLarge_img

The request is larger than the server is willing or able to process. Previously called “Request Entity Too Large”.

via Wikipedia


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 – 408 Request Timed Out

Next Post:

HTTP Status Coop – 500 Internal Server Error

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.