xavi/libweb/examples/headers, 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-02T13:48:04+00:00 examples: Add distclean target 2025-10-02T13:48:04+00:00 Xavier Del Campo Romero xavi92@disroot.org 2025-10-02T13:40:03+00:00 urn:sha1:bba0b62f4e9e17927b9a2cda51dd5a4aa1b1f14e 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. headers/main.c: Update to new handler interface 2023-11-20T16:05:21+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-11-20T16:05:21+00:00 urn:sha1:bc1d77983acd0e5160071fb724fef90ac0f9ca37 Send HTTP headers to payload callback 2023-11-18T00:03:12+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-11-17T23:56:04+00:00 urn: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.