xavi/libweb, branch v0.5.0Small and lightweight web framework written in C99 and POSIX.1-2008.
https://gitea.privatedns.org/xavi/libweb/atom?h=v0.5.02025-10-09T09:28:59+00:00Add man3 pages for the form API2025-10-09T09:28:59+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-09T09:18:03+00:00urn:sha1:de7f4b2ffcd92dfeada9235ce857b801a4851da7Free chunk/step user data on context free2025-10-07T23:57:42+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-07T23:51:15+00:00urn:sha1:e85d90fbf37cbd5a3264a2debd9b51438836c729
So far, users had no way to free user-defined data allocated inside the
chunk/step function pointers whenever an error occurred.
Now, the free callback can be also used in conjunction with chunk/step,
so that user-defined data is now deallocated when the operation
finishes (in the case of chunk-encoded data) or an error occurs.
libweb_http.7: Remove obsolete information2025-10-07T23:57:42+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-07T21:33:20+00:00urn:sha1:594917d7b2170f7e946e2cc7e9c5de3f6e4775beImplement HTTP chunk encoding2025-10-07T23:57:42+00:00Xavier Del Campo Romeroxavi92@disroot.org2025-10-06T21:01:42+00:00urn: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 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.