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

Category: HTTP Status Coops

HTTP Status Coop – 503 Service Unavailable

November 16, 2017 by Hilary

Fourteenth in the HTTP Status Coop series is 503 Service Unavailable! The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. via Wikipedia Cooper says “no way!” 😀 For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on …

Continue Reading

HTTP Status Coop – 500 Internal Server Error

November 13, 2017 by Hilary

Lucky Thirteen, on a Monday the 13th, of the HTTP Status Coop series is 500 Internal Server Error! And no, I didn’t plan it that way! A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. via Wikipedia For the entire HTTP Status Coop series that’s been released …

Continue Reading

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)! 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 …

Continue Reading

HTTP Status Coop – 408 Request Timed Out

November 7, 2017 by Hilary

Eleventh in the HTTP Status Coop series is 408 Request Timed Out! The server timed out waiting for the request. According to HTTP specifications: “The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.” via Wikipedia For …

Continue Reading

HTTP Status Coop – 406 Not Acceptable

November 2, 2017 by Hilary

Tenth in the HTTP Status Coop series is 406 Not Acceptable! The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. via Wikipedia Clearly the request was *not* acceptable for Cooper… For the entire HTTP Status Coop series that’s been released so far, head over to …

Continue Reading

HTTP Status Coop – 404 Not Found

October 30, 2017 by Hilary

Ninth in the HTTP Status Coop series is 404 Not Found! The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. 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 …

Continue Reading

HTTP Status Coop – 403 Forbidden

October 26, 2017 by Hilary

Eighth in the HTTP Status Coop series is 403 Forbidden! The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort. via Wikipedia For the entire HTTP Status Coop series that’s been released so far, head over to …

Continue Reading

HTTP Status Coop – 400 Bad Request

October 23, 2017 by Hilary

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 …

Continue Reading

HTTP Status Coop – 307 Temporary Redirect

October 18, 2017 by Hilary

Sixth in the HTTP Status Coop series is 307 Temporary Redirect! In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, …

Continue Reading

HTTP Status Coop – 305 Use Proxy

October 13, 2017 by Hilary

Fifth in the HTTP Status Coop series – 305 Use Proxy! The requested resource is available only through a proxy, the address for which is provided in the response. Many HTTP clients (such as Mozilla[26] and Internet Explorer) do not correctly handle responses with this status code, primarily for security reasons. via Wikipedia This  is a photo of my …

Continue Reading

Posts navigation

  • 1
  • 2
  • Next

Recent Posts

  • Looking back on 2018, looking forward to 2019
  • C# Advent Calendar 2018 – Can I Put All Of My Smoke Tests For A REST API In One Test? Yes!
  • Implementing RestSharp in REST API automated tests
  • TestBash Manchester Tweets!
  • Testing the UI and API together with my new practice app!

Categories

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

Upcoming Events

  1. TestBash Essentials Brighton

    April 3
  2. StarEast

    April 30
  3. StarEast

    May 1 @ 1:45 pm - 2:30 pm

View All Events

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