From 7f9ad99b8eb43d2102a383dbbaa8f0c0832bd423 Mon Sep 17 00:00:00 2001 From: Bryce Kwon Date: Fri, 16 Oct 2026 06:33:14 -1000 Subject: Answer 404 for any path below the about page The about page served every file beside the readme as a page of its own, through the about filter, and answered 200 for directories and missing files alike. Images it passed through came from the root of the default branch whatever the readme's own directory and ref. A readme on disk exposed its whole directory this way. --- source/ui-summary.h | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'source/ui-summary.h') diff --git a/source/ui-summary.h b/source/ui-summary.h index 0f61da5..ecb1a5c 100644 --- a/source/ui-summary.h +++ b/source/ui-summary.h @@ -1,14 +1,13 @@ /* * The summary and about pages, the two a repository opens with, one listing * its refs and recent commits and the other built from its readme. cmd.c - * reaches both, and it hands the about page whatever path follows the page - * name in the url, so a readme can link to a file beside it. + * reaches both. */ #ifndef CGIT_UI_SUMMARY_H #define CGIT_UI_SUMMARY_H extern void cgit_print_summary(void); -extern void cgit_print_repo_readme(const char *path); +extern void cgit_print_repo_readme(void); #endif // CGIT_UI_SUMMARY_H -- cgit