Small and lightweight web framework written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/libweb/atom?h=v0.3.0 2024-02-19T22:00:56+00:00 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. 2023-11-20T15:27:28+00:00 xavi xavi@noreply.localhost 2023-11-20T15:27:28+00:00 urn:sha1:8f1ad3124e9e063ca0ee7c2548c747b20de3529d Reviewed-on: https://gitea.privatedns.org/xavi/libweb/pulls/2 2023-11-20T15:25:58+00:00 Xavier Del Campo xavier.delcampo@midokura.com 2023-11-20T11:20:51+00:00 urn:sha1:59a67a7541ee1559b140494c21a25b195246a4fa Even if server_client_close fails, it is needed for client_free to remove the dangling reference from h->clients. 2023-11-20T15:06:19+00:00 Xavier Del Campo xavier.delcampo@midokura.com 2023-11-16T11:23:08+00:00 urn:sha1:98f5f52461b0c1ab1ee3331722bd32e2db9e1d41 Some applications might set up a struct handler object to listen on any port i.e., 0, but still need a way to determine which port number was eventually selected by the implementation. Therefore, handler_listen has been reduced to the server initialization bit, whereas the main loop has been split into its own function, namely handler_loop. Because of these changes, it no longer made sense for libweb to write the selected port to standard output, as this is something now applications can do on their own. 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. 2023-10-10T22:07:13+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-10-10T21:21:35+00:00 urn:sha1:0222b75e8554796548e079aa3393c512ae30ac24 It was found out there was another project of the same name around (https://git.sr.ht/~strahinja/slweb/), also related to website generation. In order to avoid confusion, a new name has been chosen for this project. Surprisingly, libweb was not in use by any distributions (according to https://repology.org and AUR index), and it should reflect well the intention behind this project i.e., being a library to build web-related stuff. 2023-09-07T13:41:46+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-07T13:41:46+00:00 urn:sha1:f9e3516f5026babdea65e4cb6bb3756f0f8dd25a Port numbers are unsigned by definition. Fortunately, this was a minor issues since server_init was doing an implicit cast to unsigned short. 2023-07-20T23:28:38+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-20T21:47:33+00:00 urn:sha1:8c3ba33ced08b211db0cd5f81675bdf62f55acc7 Since slweb is meant as a library, it is advisable to keep public header files under their own directory in order to avoid name clashing i.e., #include "something.h" Now becomes: #include "slweb/something.h" 2023-07-20T21:52:55+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-06-05T23:59:46+00:00 urn:sha1:35ced95c363640c3f8cd86b60330fb68338101b8 The new search feature will require them. 2023-07-20T21:52:55+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-06-05T23:58:42+00:00 urn:sha1:0759122e4c7dd17af9f981040e44c747579478b6 Future commits will make use of this function outside handler.c.