xavi/slcl/main.c, branch v0.1.0-rc2 Small and lightweight cloud storage written in C99 and POSIX.1-2008. https://gitea.privatedns.org/xavi/slcl/atom?h=v0.1.0-rc2 2023-09-15T23:46:07+00:00 main.c: Refactor calls to handler_add 2023-09-15T23:46:07+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-15T23:46:07+00:00 urn:sha1:b2037fea902cca2dd0238a1116b05480ef29b3d6 main.c: Remove string duplication in get_forms 2023-09-09T00:34:26+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-09T00:30:37+00:00 urn:sha1:e81d1f6312de85e5640277f5968263aa8cd393db slweb now assumes application/x-www-form-urlencoded-data as text, so it now returns a null-terminated string on struct http_post member "data". This removes the need for slcl to call strdup(3) in order to obtain a null-terminated string. Check directory on uploads 2023-09-08T22:50:22+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-08T22:47:14+00:00 urn:sha1:fcef3b99b86312aaeb9e1cae88179abbfda90dff For historical reasons, slweb used to check for a name called "dir" on multipart/form-data POST requests. However, stricly speaking this is application logic, so it has been now moved from slweb to slcl. This has resulted in a couple of breaking changes in slweb that had to be updated on slcl. main.c: Return 1 on null buffer 2023-09-08T22:15:39+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-09-08T22:15:39+00:00 urn:sha1:df873a988ca42d79d87acac160fdab797cb3d16d Malformed POST requests might include no payload data. However, this is not considered a fatal error, but wrong user input. Adapt to slweb's include paths 2023-07-20T23:40:55+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-20T23:24:10+00:00 urn:sha1:e49f1da7aed6894c8893cf29c33c4ca839d74976 slweb puts its header files into its own directory in order to avoid potential name clashing. Limit amount of search results 2023-07-11T11:27:49+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-11T11:11:50+00:00 urn:sha1:38f3f82a77ed4782a9c4e1b4e5a6d9d4c71390a2 When a user enters a search term that is too generic, slcl would generate a long list of search results, where this generation could have a big impact on the server performance and its available resources. Therefore, it is reasonable to limit the number of search results to an arbitrary limit, so that users are forced to enter a more specific search term in order to achieve more relevant results. cftw: Allow user callback to stop recursive search 2023-07-11T11:27:49+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-11T11:08:06+00:00 urn:sha1:59e17afe291f9df52d2334b92e88a889c2fe8f6a So far, cftw would search through all directories and files recursively, until all objects are processed. However, it is interesting for the user callback to be able to stop this process under specific circumstances. Now, cftw will pass a pointer to a bool, initialised to false by default, that can be optionally assigned to true by the user callback. Future commits will make use of this feature. For example, this will be used to limit the number of search results when a user enters a search term that is too generic and would otherwise generate a large amount of search results. main.c: Use path_isrel for search terms 2023-07-11T11:27:49+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-11T11:26:06+00:00 urn:sha1:48b171335c213091cdf682c98ad784dc5c8456da Search terms cannot use the same strict rules used for filenames or directory names, as otherwise examples such as "*folder*/*IMG*" would not work. Allow admins to define their own stylesheet 2023-07-10T23:49:12+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-10T23:20:39+00:00 urn:sha1:e79e955d93e24a192c9bf94181294d0797e9fded slcl used to provide a hardcoded stylesheet. However, it would be desirable for some admins to provide a custom stylesheet without having to rebuild the application. Now, slcl creates a default stylesheet, namely style.css, into the target directory, that can be later modified by admins. While this might contradict the suckless philosophy a bit, hopefully some admins might find this new feature useful. main.c: Disallow invalid filenames or directory names 2023-07-09T03:54:53+00:00 Xavier Del Campo Romero xavi.dcr@tutanota.com 2023-07-09T02:41:55+00:00 urn:sha1:b5282b23653b3a46ab6ae2d84049abadcc8a8a1d - Relative paths must not be used for filenames or directory names, such as "..", "." or "dir/..". - Paths with asterisks ('*') must not be allowed, to avoid confusion with wildcard expressions.