PHPNews

202 Accepted

202 Accepted , means that the server accepted the request, but it’s not sure yet if the request will be completed successfully. The specification calls it ‘intentionally non-committal’. You might see APIs using this response for for example asynchronous batch processing. HTTP doesn’t have a standard way to …

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday July 17, 2018


Bye Disqus, hello Webmention!

Since 2013 I’ve used Disqus on this website for comments. Over the years Disqus has been getting ‘fatter’, so I’ve been thinking of switching to something new. Then on Friday, I saw a tweet which got me inspired: I moved to distributed, standard based, and @indiewebcamp solutions based comments, AKA …

Continue reading »

Written by Evert Pot - - Aggregated on Monday July 16, 2018


201 Created

201 Created , just like 200 OK , means that the request was successful, but it also resulted in a new resource being created. In the case of a PUT request, it means that a new resource was created on the actual url that was specified in the request. Example PUT /new-resource HTTP/1.1 Content-Type: …

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday July 10, 2018


200 OK

200 OK is the most common HTTP status code. It generally means that the HTTP request succeeded. If the HTTP request was a GET request, the response should include the full representation of the resource. If the response has no body, then the 204 No Content response body should be used instead. Example: …

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday July 3, 2018


103 Early Hints

103 Early Hints is an experimental status code. It can be used by a server to preemptively send headers to a client or intermediary. A client might be able to use these headers to make certain optimizations as early as possible in the process. The specific use-case in RFC8297 is preloading. A server might tell …

Continue reading »

Written by Evert Pot - - Aggregated on Saturday June 30, 2018


102 Processing

102 Processing is a pretty rare status code. It’s not in the official newer HTTP specifications , and its only appearance is in an obsolete version of the WebDAV specification. It was left out of the current WebDAV specification, and more recent HTTP specifications . When the server sends back the 102 …

Continue reading »

Written by Evert Pot - - Aggregated on Friday June 29, 2018


101 Switching Protocols

101 Switching Protocols is a status code that’s used for a server to indicate that the TCP conncection is about to be used for a different protocol. The best example of this is in the WebSocket protocol . WebSocket uses a HTTP handshake when creating the connection, mainly for security reasons. When a …

Continue reading »

Written by Evert Pot - - Aggregated on Thursday June 28, 2018


100 Continue

100 Continue is a status-code you might not deal with very often. Generally, as a web developer, the 100 Continue status is sent under the hood by your webserver. So what’s it for? The best example comes from RFC 7231 . Say, you’re sending a large object to the server using a PUT request, you may include a …

Continue reading »

Written by Evert Pot - - Aggregated on Wednesday June 27, 2018


100 Continue

100 Continue is a status-code you might not deal with very often. Generally, as a web developer, the 100 Continue status is sent under the hood by your webserver. So what’s it for? The best example comes from RFC 7231 . Say, you’re sending a large object to the server using a PUT request, you may include a …

Continue reading »

Written by Evert Pot - - Aggregated on Wednesday June 27, 2018


Series of posts on HTTP status codes

Because I want to get into the habit of blogging on a regular basis, I thought it would be a fun idea to write a series of articles on one of my favourite topics: HTTP and Webservices. To start, I began writing an article for every HTTP status code. I only realized after I drafted the first few, that the IANA …

Continue reading »

Written by Evert Pot - - Aggregated on Wednesday June 27, 2018


Series of posts on HTTP status codes

Because I want to get into the habit of blogging on a regular basis, I thought it would be a fun idea to write a series of articles on one of my favourite topics: HTTP and Webservices. To start, I began writing an article for every HTTP status code. I only realized after I drafted the first few, that the IANA …

Continue reading »

Written by Evert Pot - - Aggregated on Wednesday June 27, 2018


Ketting 2.0 release

Being fresh out of a job, I had some time to work on a new release of the Ketting library. The Ketting library is meant to be a generic HATEOAS library for Javascript using a simple, modern API. Currently it only supports the HAL and HTML formats, but I’m curious what other formats folks are interested to …

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday June 19, 2018


Ketting 2.0 release

Being fresh out of a job, I had some time to work on a new release of the Ketting library. The Ketting library is meant to be a generic HATEOAS library for Javascript using a simple, modern API. Currently it only supports the HAL and HTML formats, but I’m curious what other formats folks are interested to …

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday June 19, 2018


A HTTP structured-header parser for Javascript

A new draft is underway for HTTP, that has a good chance of becoming an RFC. The draft is titled “Structured Headers for HTTP” and defines a standard way to: Encode a list of items in HTTP headers Encode a dictionary (hash, map, associative array depending on where you’re from). Encode a ‘parameterize…

Continue reading »

Written by Evert Pot - - Aggregated on Tuesday March 27, 2018


Ketting 1.0 release.

Since 2016 I’ve been working on a javascript library to make it easier to work with HAL REST services. Yesterday I realized I implemented all the features I wanted for a 1.0 release, and also that I never talked about it on this blog. So this evening I released 1.0, and also share some information about it …

Continue reading »

Written by Evert Pot - - Aggregated on Monday March 26, 2018


I work at Yelp now!

In a twisted turn of events, I suddenly find myself to be working for Yelp ! It sounds a bit like it was a surprise, and it kind of was. Only 6 months after I started my job at Turnstyle , it got acquired by Yelp . I would joke “I must have done something right”, but the truth is that I work with some extremely …

Continue reading »

Written by Evert Pot - - Aggregated on Friday April 21, 2017