xavi/libweb/doc, branch fixesSmall and lightweight web framework written in C99 and POSIX.1-2008.
https://gitea.privatedns.org/xavi/libweb/atom?h=fixes2024-08-22T00:27:35+00:00Bump version to 0.4.02024-08-22T00:27:35+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-22T00:04:29+00:00urn:sha1:93571556ee97e1a3e1829f8bc708d1d63f188840Move signal handling to processes2024-08-22T00:27:34+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-08-19T22:07:05+00:00urn:sha1:43e89fb23943b5ffb6854f290592c29cd079bf46
So far, libweb installed a signal handler so as to handle SIGTERM,
SIGPIPE and SIGINT signals so that processes would not have to care
about such details.
However, it is not advisable for libraries to install signal handlers,
as signals are handled on a per-process basis. The previous approach
would be incompatible if several instances of the library were allocated
by the same process.
Unfortunately, this has the undesired side effect of adding the
boilerplate code into the process.
Bump version to 0.3.02024-02-19T22:33:27+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-19T22:29:01+00:00urn:sha1:b4930f72bb9026c5a0871f4fa4cabe20cb0e6a9fLimit maximum multipart/form-data pairs and files2024-02-19T22:00:56+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-19T22:00:56+00:00urn:sha1:afe0681c0b26bb64bad55d7e86770f346cfa043e
A malicious user could inject an infinite number of empty files or
key/value pairs into a request in order to exhaust the device's
resources.
Bump version to 0.2.02024-02-12T22:12:43+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-12T20:21:57+00:00urn:sha1:6ceae16a20175edb77fb2ffab0d3d6648d011221libweb_http.7: Update according to status quo2024-02-12T22:00:03+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-12T21:44:47+00:00urn:sha1:edc855f93b10aebc7afc71749ba2e86c73b1b77clibweb_html.7: Fix typo2024-02-12T21:52:18+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-12T21:52:12+00:00urn:sha1:f9a305fe4d71d5940184d8ca850241558b36c315Update copyright notices to 20242024-02-12T21:45:17+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2024-02-12T21:16:35+00:00urn:sha1:fcba916011f8fe21e60df1e0302371fc3956126fdoc: Update handler_{loop,listen}2023-11-20T15:08:08+00:00Xavier Del Campoxavier.delcampo@midokura.com2023-11-16T11:21:31+00:00urn:sha1:2561ec32fe24e9cc81151193fbf2c55c94078816Send HTTP headers to payload callback2023-11-18T00:03:12+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2023-11-17T23:56:04+00:00urn:sha1:65031ca3502e0c27780be847fd97c112546741a9
Even if libweb already parses some common headers, such as
Content-Length, some users might find it interesting to inspect which
headers were received from a request.
Since HTTP/1.1 does not define a limit on the number of maximum headers
a client can send, for security reasons a maximum value must be provided
by the user. Any extra headers shall be then discarded by libweb.
An example application showing this new feature is also provided.