Monthly Archives: October 2017
HTTP Status Coop – 404 Not Found
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 blog!
HTTP Status Coop – 403 Forbidden
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 the HTTP Status Coop page on my blog!
HTTP Status Coop – 400 Bad Request
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 been released so far, head over to the HTTP Status Coop page on my blog!
HTTP Status Coop – 307 Temporary Redirect
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, a POST request should be repeated using another POST request.
via Wikipedia
My husband, lovingly redirecting Cooper out of the snow 😀
For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
HTTP Status Coop – 305 Use Proxy
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 custom Big Head (from Fathead) of Cooper, that sits at my desk! It’s my proxy for interacting with my dog while at work 😀
For the entire HTTP Status Coop series that’s been released so far, head over to the HTTP Status Coop page on my blog!
HTTP Status Coop – 303 See Other
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 URI.
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!
HTTP Status Coop – 206 Partial Content
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 Wikipedia
