| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | examples: Add distclean target | Xavier Del Campo Romero | 2025-10-02 | 1 | -0/+3 |
| | | |||||
| * | Move signal handling to processes | Xavier Del Campo Romero | 2024-08-22 | 1 | -6/+69 |
| | | | | | | | | | | | | | | | 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 | Xavier Del Campo Romero | 2023-11-20 | 1 | -2/+11 |
| | | |||||
| * | Send HTTP headers to payload callback | Xavier Del Campo Romero | 2023-11-18 | 4 | -0/+127 |
| 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. | |||||
