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

Month: October 2017

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

HTTP Status Coop – 303 See Other

October 10, 2017 by Hilary

Fourth post in the HTTP Status Coop series – 303 See Other! The response to the request can be found under another URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the data and should issue a new GET request to the given …

Continue Reading

HTTP Status Coop – 206 Partial Content

October 5, 2017 by Hilary

Third post in the HTTP Status Coop series – 206 Partial Content! The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams. via …

Continue Reading

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.