Small and lightweight web framework written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/libweb/atom?h=v0.6.0 2026-02-12T16:01:01+00:00 2026-02-12T16:01:01+00:00 Xavier Del Campo Romero xavi92@disroot.org 2026-02-12T16:01:01+00:00 urn:sha1:f6f7d6b05b66307aef549086f8dea24f530f49e8 When the call to realloc(3) returns successfully, h->elem must be updated immediately. Otherwise, a failed call to strdup(3) would cause the caller to free h->elem at shutdown, but h->elem would still contain a dangling pointer, and therefore cause undefined behaviour. 2026-02-12T15:59:55+00:00 Xavier Del Campo Romero xavi92@disroot.org 2026-02-12T15:59:55+00:00 urn:sha1:87807c690947f4636dc4dd7fddca15f944719f0c Users might want to know which HTTP operation (i.e., POST or PUT) and/or resource is being requested before determining whether the request should be accepted or not. 2026-01-31T22:16:16+00:00 Xavier Del Campo Romero xavi92@disroot.org 2026-01-30T23:49:44+00:00 urn:sha1:abd5fc025054af2bde355553e5307c94e994a8d9 The free callback is meant to be executed whenever libweb fails to execute something and let the user deallocate any pending memory. However, the payload callback should deallocate user memory by itself on failure, since relying on the free payload for this purpose is not intuitive and fragile. 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. 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. 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. 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. 2024-08-25T12:31:21+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2024-08-25T12:31:21+00:00 urn:sha1:43a39a1f2e5e6c7c520f03293fc57aa76fea8aaf libweb is meant to be silent during normal operation, thus only printing to stderr on errors. 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. 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.