xavi/libweb/include, branch test-mf Small and lightweight web framework written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/libweb/atom?h=test-mf 2025-10-07T23:57:42+00:00 Implement HTTP chunk encoding 2025-10-07T23:57:42+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-06T21:01:42+00:00 urn:sha1:e77bd93693a74ce872d4c13fb45537c34518d84f A new function pointer, namely chunk, has been added to struct http_response so that library users can generate their message bodies dynamically. Allow custom backlog connections 2025-10-06T19:03:59+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-06T19:03:59+00:00 urn:sha1:db9cb051c4ee05c07ab32dfed5bae8b7dc0916bd libweb calls listen(2) when setting up the HTTP server, and its backlog argument was hardcoded to 10. While probably not an issue for some applications, it can be too limiting for some others. Therefore, it is desirable to allow library users to set up their own limits. Otherwise, 10 is still chosen as a sane default. Fix design issues with async responses, add async example 2025-10-06T13:51:00+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-05T23:23:20+00:00 urn:sha1:3e4c7c993bbbe2bdeb563fa888b900d01c4be4a1 struct http_response did not provide users any void * that could be used to maintain a state between calls to an asynchronous HTTP response. On the other hand, the user pointer could not be used for this purpose, since it is shared among all HTTP clients for a given struct handler instance. Moreover, the length callback was still not supporting this feature, which in fact might be required by some users. Implementing this was particularly challenging, as this broke the current assumption that all bytes on a call to http_read were being processed. Now, since a client request can only be partially processed because of the length callback, http_read must take this into account so that the remaining bytes are still available for future calls, before reading again from the file descriptor. Implement form interface 2025-10-02T13:52:14+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-09-30T21:50:33+00:00 urn:sha1:a0f5f7509bb9040752fa61fe0fdb447608e22b1c This new interface allows library users to parse application/x-www-form-urlencoded data conveniently. html: Make html_encode public 2025-09-27T22:12:57+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-09-27T18:48:55+00:00 urn:sha1:94ddbec88e57fe742f219a30145650165887f22c Among other reasons, this function can be useful to sanitize user-generated content before assigning it do a node. Implement async HTTP responses 2025-09-24T10:33:35+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-09-23T20:03:57+00:00 urn:sha1:5a6f30440b66fe6713acb9d979dc3e6624e4c36a Sometimes, library users cannot return a HTTP response as soon as the request is received, or the operations that are required to generate it can take a long time. In order to solve this, libweb adds a new member to struct http_response, namely step, which must be assigned to a function whenever a HTTP response should be generated in a non-blocking manner. Leaving the function pointer as null will fall back to the default behaviour. Implement HTTP byte serving 2024-11-10T23:04:39+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2024-11-10T22:56:57+00:00 urn:sha1:5d47b2d12caba33793a078d2eafae6ae3d2ad921 This commit allows the HTTP server to return partial content to clients, rather than returning the whole resource. This can be particularly useful for applications such as audio/video playback or showing large PDF files. Notes: - Applications must not care about partial contents i.e., if a valid user request was made, applications must still return HTTP status 200 ("OK"), as usual. The HTTP server will then translate the status code to 206 ("Partial Content") if required. Move signal handling to processes 2024-08-22T00:27:34+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2024-08-19T22:07:05+00:00 urn: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. Limit maximum multipart/form-data pairs and files 2024-02-19T22:00:56+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2024-02-19T22:00:56+00:00 urn: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. http: Add support for PUT 2023-11-20T15:34:24+00:00 Xavier Del Campo xavier.delcampo@midokura.com 2023-11-17T11:53:59+00:00 urn:sha1:1755ee663cd67cd8d9adf9f06dd82b0477adab76 Notes: - Since curl would use the "Expect: 100-continue" header field for PUT operations, this was a good operation to fix the existing issues in its implementation. Breaking changes: - expect_continue is no longer exclusive to struct http_post. Now, it has been moved into struct http_payload and it is up to users to check it.