We just released version 7 of Ketting. Ketting is a generic HATEOAS client for Javascript. A whole bunch of features have been added since September. We’ve been testing Ketting 7 in beta since January, so I’m excited to get this out the door. I’ve been working on this project since…

Curveball is the freshest new microframework for Typescript. Since the last big announcement, there’s been a number new curveball users, and also a few framework changes. I thought it would be nice to list some of the things we’ve been working on this month. Starter template Probably the most significant, curveball now…

Since mid-2018 we’ve been working on a new micro-framework, written in typescript. The framework competes with Express, and takes heavy inspiration from Koa. It’s called Curveball. If you only ever worked with Express, I feel that for most people this project will feel like a drastic step up. Express was…

When you’re building Hypermedia-style services, you might have used the IANA link relation types list to find appropriate, generic keywords for your rel="" attributes. This list is the official registry for relation types such as collection, next, canonical and others. I had a need for adding a few generic relationship…

I was a bit frustrated with the existing offerings for OAuth2 clients in Javascript. I heavily use the Fetch API directly, but Web API’s haven’t really caught up to have deep integration with OAuth2. We were using client-oauth2, but the minified size of this library was close to 40kb which…

203 Non-Authoritative Information is a status-code that might be used by a HTTP proxy. A HTTP Proxy sits in the middle between a client and a server (origin). In some cases a HTTP Proxy might make changes to the response before it reaches the client. Perhaps because the Proxy converts…

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 communicate after a request if a request eventually succeeded. An API using this might use some other facility to later to do this.

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…