xavi/libweb, branch chunkSmall and lightweight web framework written in C99 and POSIX.1-2008.
https://gitea.privatedns.org/xavi/libweb/atom?h=chunk2025-10-07T10:43:25+00:00WIP chunk encoding2025-10-07T10:43:25+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-06T21:01:42+00:00urn:sha1:b9d9328956c656f0e9a007b8810cadafbe531c48Allow custom backlog connections2025-10-06T19:03:59+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-06T19:03:59+00:00urn: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.
libweb_http.7: Add note about HTTP responses2025-10-06T14:27:21+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-06T14:27:21+00:00urn:sha1:4918cf87d3cf5d3dd8425fe10d97a06282472df6Fix design issues with async responses, add async example2025-10-06T13:51:00+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-05T23:23:20+00:00urn: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 interface2025-10-02T13:52:14+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-09-30T21:50:33+00:00urn:sha1:a0f5f7509bb9040752fa61fe0fdb447608e22b1c
This new interface allows library users to parse
application/x-www-form-urlencoded data conveniently.
examples: Add distclean target2025-10-02T13:48:04+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-02T13:40:03+00:00urn:sha1:bba0b62f4e9e17927b9a2cda51dd5a4aa1b1f14eexamples/Makefile: Increase flexibility2025-10-02T13:48:04+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-02T13:44:30+00:00urn:sha1:9be656dfed53783036c7ae1edae04060b451d6df
The former implementation required redundant code for every new
directory.
html.c: Replace \n with <br> on html_encode2025-09-27T22:13:42+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-09-27T22:13:17+00:00urn:sha1:a13b91d64c96670caff1ea9830b7e4a90ad81eaa
This replacement can come in handy for library users dealing with
multi-line user-generated content.
html: Make html_encode public2025-09-27T22:12:57+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-09-27T18:48:55+00:00urn:sha1:94ddbec88e57fe742f219a30145650165887f22c
Among other reasons, this function can be useful to sanitize
user-generated content before assigning it do a node.
html.c: Do not recurse on siblings2025-09-27T18:48:09+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-09-27T18:48:09+00:00urn:sha1:bdfbd076f2d3e7212f300bf5edbbad1934fae324
It is not required to do so. Otherwise, nodes with many siblings could
lead to a very deep call stack for no reason.