<feed xmlns='http://www.w3.org/2005/Atom'>
<title>xavi/libweb/doc/man7/libweb_handler.7, branch chunk</title>
<subtitle>Small and lightweight web framework written in C99 and POSIX.1-2008.
</subtitle>
<id>https://gitea.privatedns.org/xavi/libweb/atom?h=chunk</id>
<link rel='self' href='https://gitea.privatedns.org/xavi/libweb/atom?h=chunk'/>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/'/>
<updated>2025-10-06T19:03:59+00:00</updated>
<entry>
<title>Allow custom backlog connections</title>
<updated>2025-10-06T19:03:59+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi92@disroot.org</email>
</author>
<published>2025-10-06T19:03:59+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=db9cb051c4ee05c07ab32dfed5bae8b7dc0916bd'/>
<id>urn:sha1:db9cb051c4ee05c07ab32dfed5bae8b7dc0916bd</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Bump version to 0.4.0</title>
<updated>2024-08-22T00:27:35+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-22T00:04:29+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=93571556ee97e1a3e1829f8bc708d1d63f188840'/>
<id>urn:sha1:93571556ee97e1a3e1829f8bc708d1d63f188840</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump version to 0.3.0</title>
<updated>2024-02-19T22:33:27+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-19T22:29:01+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=b4930f72bb9026c5a0871f4fa4cabe20cb0e6a9f'/>
<id>urn:sha1:b4930f72bb9026c5a0871f4fa4cabe20cb0e6a9f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Limit maximum multipart/form-data pairs and files</title>
<updated>2024-02-19T22:00:56+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-19T22:00:56+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=afe0681c0b26bb64bad55d7e86770f346cfa043e'/>
<id>urn:sha1:afe0681c0b26bb64bad55d7e86770f346cfa043e</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Bump version to 0.2.0</title>
<updated>2024-02-12T22:12:43+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-12T20:21:57+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=6ceae16a20175edb77fb2ffab0d3d6648d011221'/>
<id>urn:sha1:6ceae16a20175edb77fb2ffab0d3d6648d011221</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update copyright notices to 2024</title>
<updated>2024-02-12T21:45:17+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-12T21:16:35+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=fcba916011f8fe21e60df1e0302371fc3956126f'/>
<id>urn:sha1:fcba916011f8fe21e60df1e0302371fc3956126f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: Update handler_{loop,listen}</title>
<updated>2023-11-20T15:08:08+00:00</updated>
<author>
<name>Xavier Del Campo</name>
<email>xavier.delcampo@midokura.com</email>
</author>
<published>2023-11-16T11:21:31+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=2561ec32fe24e9cc81151193fbf2c55c94078816'/>
<id>urn:sha1:2561ec32fe24e9cc81151193fbf2c55c94078816</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Send HTTP headers to payload callback</title>
<updated>2023-11-18T00:03:12+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-11-17T23:56:04+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=65031ca3502e0c27780be847fd97c112546741a9'/>
<id>urn:sha1:65031ca3502e0c27780be847fd97c112546741a9</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Rename project from slweb to libweb</title>
<updated>2023-10-10T22:07:13+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2023-10-10T21:21:35+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=0222b75e8554796548e079aa3393c512ae30ac24'/>
<id>urn:sha1:0222b75e8554796548e079aa3393c512ae30ac24</id>
<content type='text'>
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.
</content>
</entry>
</feed>
