<feed xmlns='http://www.w3.org/2005/Atom'>
<title>xavi/libweb, branch v0.4.0</title>
<subtitle>Small and lightweight web framework written in C99 and POSIX.1-2008.
</subtitle>
<id>https://gitea.privatedns.org/xavi/libweb/atom?h=v0.4.0</id>
<link rel='self' href='https://gitea.privatedns.org/xavi/libweb/atom?h=v0.4.0'/>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/'/>
<updated>2024-08-22T00:27:35+00:00</updated>
<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>Move signal handling to processes</title>
<updated>2024-08-22T00:27:34+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-19T22:07:05+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=43e89fb23943b5ffb6854f290592c29cd079bf46'/>
<id>urn:sha1:43e89fb23943b5ffb6854f290592c29cd079bf46</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>http.c: Fix ending boundaries not followed by CRLF</title>
<updated>2024-08-22T00:27:34+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-21T23:56:20+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=34b62bd0c47c915a12ff1b81f52b123fc3eb4a69'/>
<id>urn:sha1:34b62bd0c47c915a12ff1b81f52b123fc3eb4a69</id>
<content type='text'>
According to RFC 2046, section 5.1.1, end boundaries might not be
followed by CRLF. However, so far libweb naively relied on this
behaviour as major implementations, such as cURL, Chromium or Gecko
always add the optional CRLF, whereas Dillo does not.
</content>
</entry>
<entry>
<title>http.c: Accept double quotes on boundaries</title>
<updated>2024-08-22T00:27:34+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-21T21:33:00+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=3a25e79f269aa171f4e5646d52eb2f90d275cb3c'/>
<id>urn:sha1:3a25e79f269aa171f4e5646d52eb2f90d275cb3c</id>
<content type='text'>
"multipart/form-data"-encoded POST requests might use double quotes for
their boundaries. While this is required when invalid characters are
otherwise used (e.g.: ':'), some web clients always insert double
quotes.

Additionally, according to RFC 2046 section 5.1.1, the boundary
parameter consists of 1 to 70 characters, but libweb was not imposing
such restrictions.
</content>
</entry>
<entry>
<title>http.c: Remove unneeded parameter</title>
<updated>2024-08-22T00:27:34+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-21T21:55:21+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=700ae79d57b1d78551d984ce2dc886a310cc6be8'/>
<id>urn:sha1:700ae79d57b1d78551d984ce2dc886a310cc6be8</id>
<content type='text'>
This parameter was rendered obsolete after the following commit:

commit b0accd099fa8c5110d4c3c68830ad6fd810ca3ec
Author: Xavier Del Campo Romero &lt;xavi.dcr@tutanota.com&gt;
Date:   Fri Nov 24 00:52:50 2023 +0100

    http.c: Unify read operations
</content>
</entry>
<entry>
<title>http.c: Remove unused variable</title>
<updated>2024-08-22T00:27:34+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-21T21:15:44+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=915be88ddcebac61dc06cc47668961b602e01b38'/>
<id>urn:sha1:915be88ddcebac61dc06cc47668961b602e01b38</id>
<content type='text'>
</content>
</entry>
<entry>
<title>http.c: Fix memory leak on read failure</title>
<updated>2024-08-22T00:27:33+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-22T00:18:14+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=15686de86f15866041107bd9830834636008fe1b'/>
<id>urn:sha1:15686de86f15866041107bd9830834636008fe1b</id>
<content type='text'>
For some unknown reason, ctx_free was only called by update_lstate, but
this is not the only function that modifies a struct ctx instance. Since
struct ctx is related to read operations, ctx_free must instead be
called whenever http_read fails.
</content>
</entry>
<entry>
<title>http.c: Fix wrong check</title>
<updated>2024-08-22T00:24:42+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-08-21T21:14:20+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=407b5d32156d60420f83d6e0567e9b3e9c878ad9'/>
<id>urn:sha1:407b5d32156d60420f83d6e0567e9b3e9c878ad9</id>
<content type='text'>
p-&gt;f is a FILE *, so it is invalid to check against negative values.

This bug was introduced when p-&gt;fd, a file descriptor, was replaced with
p-&gt;f, a FILE *, by the following commit:

commit b0accd099fa8c5110d4c3c68830ad6fd810ca3ec
Author: Xavier Del Campo Romero &lt;xavi.dcr@tutanota.com&gt;
Date:   Fri Nov 24 00:52:50 2023 +0100

    http.c: Unify read operations
</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>CMakeLists.txt: Fix dynstr version</title>
<updated>2024-02-19T22:28:12+00:00</updated>
<author>
<name>Xavier Del Campo Romero</name>
<email>xavi.dcr@tutanota.com</email>
</author>
<published>2024-02-19T22:28:09+00:00</published>
<link rel='alternate' type='text/html' href='https://gitea.privatedns.org/xavi/libweb/commit/?id=d9836a5b42337fffc61dab176105fc68547695aa'/>
<id>urn:sha1:d9836a5b42337fffc61dab176105fc68547695aa</id>
<content type='text'>
It was accidentally bumped to 0.2.0 during libweb's 0.2.0 release.
</content>
</entry>
</feed>
