Web servers use the request's path and HTTP method to look up the correct resource, refers as "routing".
We can define a route by calling a method named after HTTP verbs, passing a path and a function to execute when matched.
We can access the web server by going to http://localhost:3000
This code create a web server running at port 3000, and register the following path with the GET method which response as follows:
There are many HTTP methods to use in a different situation, for instance.
Requests using GET should only retrieve data.
Submits a payload to the specified resource, often causing state change or side effect.
Replaces all current representations of the target resource using the request's payload.
Deletes the specified resource.
To handle each of the different verbs, @teakit/core has a built-in API for several HTTP verbs by default, similar to Application.get
Application HTTP methods accepts the following parameters:
You can read more about the HTTP methods on HTTP Request Methods.
Most developers use REST clients like Postman, Insomnia or Hoppscotch to test their API.
However, Teakit can be programmatically test using Application.handle
.
Application.handle is a function to process an actual request sent to the server.
We can accept custom HTTP Methods with Application.route
.
Application.route accepts the following:
When navigating to each method, you should see the results as the following:
Based on RFC 7231, HTTP Verb is case-sensitive.
It's recommended to use the UPPERCASE convention for defining a custom HTTP Verb with Application.
Application provides an Application.all
for handling any HTTP method for a specified path using the same API like Application.get and Application.post
Any HTTP method that matches the path, will be handled as follows:
If no path matches the defined routes, Teakit will pass the request to error
life cycle before returning a "NOT_FOUND" with an HTTP status of 404.
We can handle a custom 404 error by returning a value from 'error` life cycle like this:
When navigating to your web server, you should see the result as follows: