README.md: Update according to status quo

This commit is contained in:
Xavier Del Campo Romero 2024-02-12 23:11:36 +01:00
parent 444563ca13
commit 46a9d4efb9
Signed by: xavi
GPG Key ID: 84FF3612A9BF43F2
1 changed files with 4 additions and 4 deletions

View File

@ -12,7 +12,7 @@ portability, minimalism, simplicity and efficiency.
## Features ## Features
- Small and portable HTTP/1.1 server implementation, with support for - Small and portable HTTP/1.1 server implementation, with support for
`GET` and `POST`. `GET`, `HEAD`, `PUT` and `POST`.
- Provides a interface to set up user-defined callbacks depending on - Provides a interface to set up user-defined callbacks depending on
the operation (see example below). the operation (see example below).
- Transport-agnostic implementation. - Transport-agnostic implementation.
@ -20,8 +20,8 @@ the operation (see example below).
provided, the HTTP interface can be mapped to any other reliable provided, the HTTP interface can be mapped to any other reliable
transport layer. transport layer.
- Supports [`multiform/form-data`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST) - Supports [`multiform/form-data`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/POST)
, which makes it useful to transfer large amounts of data, such as , which makes it useful to transfer multiple files with a single `POST`
binary files. request.
- [A library](include/libweb/html.h) to write HTML programmatically. - [A library](include/libweb/html.h) to write HTML programmatically.
### TLS ### TLS
@ -156,7 +156,7 @@ $ cmake --build .
## Why this project? ## Why this project?
Originally, `libweb` was part of the Originally, `libweb` was part of the
[`slcl`](https://gitea.privatedns.org/xavi92/slcl) project, a lightweight [`slcl`](https://gitea.privatedns.org/xavi/slcl) project, a lightweight
cloud solution also written in C99 plus POSIX extensions. However, there cloud solution also written in C99 plus POSIX extensions. However, there
always was a clear separation between application logic and the underlying always was a clear separation between application logic and the underlying
HTTP/1.1 server implementation and other surrounding utilities. HTTP/1.1 server implementation and other surrounding utilities.