External/cloud-hypervisor
1
0
Fork 0
mirror of https://github.com/cloud-hypervisor/cloud-hypervisor.git synced 2024-10-02 11:35:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: Fix broken link for micro_http website

Browse Source 
Signed-off-by: Ravi kumar Veeramally <ravikumar.veeramally@intel.com>
This commit is contained in:
Ravi kumar Veeramally 2023-03-09 17:03:36 +02:00 committed by Bo Chen
parent 7b2ebd2fa5
commit 44452cbe22
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/api.md
View File

@ -221,7 +221,7 @@ The CLI options are parsed by the
[internal API](#internal-api) commands. [internal API](#internal-api) commands.
The REST API is processed by an HTTP thread using the 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 crate. As with the CLI, the HTTP requests eventually get translated into
[internal API](#internal-api) commands. [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 1. The Cloud Hypervisor HTTP thread sends the formed HTTP response back to the
user. This is abstracted by 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. crate.