xavi/libweb/examples/Makefile, branch masterSmall and lightweight web framework written in C99 and POSIX.1-2008.
https://gitea.privatedns.org/xavi/libweb/atom?h=master2025-10-06T13:51:00+00:00Fix 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.
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.
Add PUT server example2023-11-20T15:34:24+00:00Xavier Del Campoxavier.delcampo@midokura.com2023-11-17T15:34:45+00:00urn:sha1:dc8b14d99028b9235aa7d7633906a979aa08e4f9Send 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.
examples/Makefile: Add html example2023-09-24T22:18:41+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2023-09-24T22:18:41+00:00urn:sha1:d9dbad1bc63e0b2442ff81f8e839391a7e27c583Add hello world example2023-08-08T22:32:13+00:00Xavier Del Campo Romeroxavi.dcr@tutanota.com2023-08-06T14:43:57+00:00urn:sha1:4ee88984fcca86c5b0c9c4bbb7e9148c7d2fe9db