From 44452cbe2250865c1687ac8a5df45f86162729ec Mon Sep 17 00:00:00 2001 From: Ravi kumar Veeramally Date: Thu, 9 Mar 2023 17:03:36 +0200 Subject: [PATCH] doc: Fix broken link for micro_http website Signed-off-by: Ravi kumar Veeramally --- docs/api.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/api.md b/docs/api.md index 61dad8a94..9be4b62c4 100644 --- a/docs/api.md +++ b/docs/api.md @@ -221,7 +221,7 @@ The CLI options are parsed by the [internal API](#internal-api) commands. The REST API is processed by an HTTP thread using the -[Firecracker's `micro_http`](https://github.com/firecracker-microvm/firecracker/tree/master/src/micro_http) +[Firecracker's `micro_http`](https://github.com/firecracker-microvm/micro-http) crate. As with the CLI, the HTTP requests eventually get translated into [internal API](#internal-api) commands. @@ -379,5 +379,5 @@ APIs work together, let's look at a complete VM creation flow, from the ``` 1. The Cloud Hypervisor HTTP thread sends the formed HTTP response back to the user. This is abstracted by the - [micro_http](https://github.com/firecracker-microvm/firecracker/tree/master/src/micro_http) + [micro_http](https://github.com/firecracker-microvm/micro-http) crate.