cgit 1.2.3: lighttpd 1.4.57, AlpineLinux [edge]: using cache breaks delivery

Steffen Nurpmeso steffen at sdaoden.eu
Mon Dec 21 17:26:19 CET 2020


Hello.

My first post here, so first a "Thank you!", i am using cgit on
lighttpd on Linux for half a decade, and it just works (after
finally having a usable configuration).

I discovered today that cgit no longer delivers pages, and it must
have been like that for some time.  The server looks show
successful delivery, the cgit cache is populated and rotated just
correctly, but all cgit delivers is that final error of main() as

  <div class='error'>Error processing page: Invalid argument (22)</div>

(surely a misconfiguration that this is not a real HTML page,
i recall it took some time to figure out about about-filter, just
"doing it" (<pre>cat(1)</pre>)).

If i set "cache-size=0" then the desired page is delivered.
Note the cache itself is managed as usual with the default
cache-size=1999.

The files in the cache are 0600, i thought maybe that was it, but
the setting is actively reverted to this mask (i never looked at
cgit code except grepping the error).  It has always been so, the
oldest cache entry was

  -rw-------    1 lighttpd lighttpd      3023 Mar 18  2018 d2200000

I am pretty sure cgit delivered some weeks ago, the most notable
difference is that AlpineLinux switched to Lighttpd 1.4.56 then
.57, which seems to have brought tremendous changes under the
hood, like HTTP/2 support and OCSP as well as support for all the
different TLS libraries, whereas before it only was OpenSSL and
compatibles, i think.  We have HTTP/2 not enabled yet.

Anything i can do about this?

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)


More information about the CGit mailing list