Your message dated Tue, 10 May 2022 13:22:57 -0400 with message-id <Ynqfccu6tkW+PqFz@xps13> and subject line Re: Bug#1010809: lighttpd: variant without CGI or any other bells and whistles has caused the Debian Bug report #1010809, regarding lighttpd: variant without CGI or any other bells and whistles to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1010809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010809 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lighttpd Severity: wishlist -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 While looking for replacement to micro-httpd, I found lighttpd suitable (still maintained upstream and reputable codebase), but would prefer a variant that can only serve static files and respond to HTTP request codes such as If-Modified-Since, but none of the bells and whistles such as CGI and vhosts. As far as I can tell, ./configure toggles could be used to produce such a package. Alternately, changing the build options so that all bells and whistles are thereafter separate module packages would work also. Thanks! Martin-Éric - -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads) Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lighttpd depends on: ii init-system-helpers 1.60 ii libc6 2.31-13+deb11u3 ii libcrypt1 1:4.4.18-4 ii libnettle8 3.7.3-1 ii libpcre3 2:8.39-13 ii libxxhash0 0.8.0-2 ii lsb-base 11.1.0 ii mime-support 3.66 Versions of packages lighttpd recommends: pn lighttpd-mod-deflate <none> pn lighttpd-mod-openssl <none> ii perl 5.32.1-4+deb11u2 pn spawn-fcgi <none> Versions of packages lighttpd suggests: pn apache2-utils <none> pn lighttpd-doc <none> pn lighttpd-mod-authn-gssapi <none> pn lighttpd-mod-authn-pam <none> pn lighttpd-mod-authn-sasl <none> pn lighttpd-mod-geoip <none> pn lighttpd-mod-maxminddb <none> pn lighttpd-mod-trigger-b4-dl <none> pn lighttpd-mod-vhostdb-pgsql <none> pn lighttpd-mod-webdav <none> pn lighttpd-modules-dbi <none> pn lighttpd-modules-ldap <none> pn lighttpd-modules-lua <none> pn lighttpd-modules-mysql <none> ii openssl 1.1.1n-0+deb11u1 pn php-cgi <none> pn php-fpm <none> pn rrdtool <none> -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmJ6f98ACgkQrh+Cd8S0 17ZanQ/+MD1bRt9yQ23xaeCqXtUeCkkVuIedahChvaG3lWmH3YpheX2rNCyXrwoQ HycBlymv/xBgTf87khlpcUUl6W4dlZSb0UuS3LcIKBUPFvANtABGJMz1go+oeVm+ mD4dAkPiV/2daNMxKCH2PW3GDpOR7Ehsm4yLG+UpCnb82FkB4vWRE1vHQEHo3Bil 10aWhBqGQGYxam2VsgrsulH3VjR1NQ5ZhpgtaxTOUAmvlOLr9iTlpFA10V39zcnT QFl09c8yTTlX4bbY+bYeWL8GzlK4VBvUzrRPg45WjHKKRExH4IWyojlfnLVkgTgT Z2D7nVBvFkjg7bvL1NCP+P+shngjORhBroe0RjPBE9JfdOUcVp62F5oMcbngJ6hi 6yBUKABL4N5JvfPLDN1z7goLHKFl8jP3XyzIJsvIjBGpxYld02ly4+6HDbFJnNr8 i/RMQh0mk2x/T3ijEMrOU2xx3xX7Xkj6b9a2ZyzSqS6+1WJgqrfFeucap1kD5FBT /Ukl9OmLxJS0S4AvVjhAficsw5/pAFxaKcUsuEjhoTKU9l6GIPYefau2XSjDxvgB WcYRTjyVnHAiji7PDlYiRGyP88l/QKKZkUyO+sDFXJPYriZ37Rpn2f7SPUenNPFN yQjYQVkYA0VcIs+v59ncoO400XIKZ+6qPRkmr6CntWzN9HxZ3bw= =288U -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---On Tue, May 10, 2022 at 06:08:15PM +0300, Martin-Éric Racine wrote: > While looking for replacement to micro-httpd, I found lighttpd suitable > (still maintained upstream and reputable codebase), but would prefer a > variant that can only serve static files and respond to HTTP request codes > such as If-Modified-Since, but none of the bells and whistles such as CGI and > vhosts. As far as I can tell, ./configure toggles could be used to produce > such a package. Alternately, changing the build options so that all bells and > whistles are thereafter separate module packages would work also. lighttpd is modular. The Debian lighttpd package is built in such a way as to provide multiple options for configuration, as directed by your lighttpd.conf. lighttpd can be already be configured to use only the lighttpd module which serves static files. A simple lighttpd.conf which serves only static files: server.document-root = "/var/www" # path to your document root (Yes, that's it: one line. lighttpd listens on port 80 by default.) A simple lighttpd.conf which serves only static files and does not even load default modules mod_indexfile and mod_dirlisting into memory: server.document-root = "/var/www" # path to your document root server.compat-module-load = "disable" server.modules += ("mod_staticfile") lighttpd is already lightweight and has been used in numerous commercial consumer routers which have only 64 MB of memory. If for some reason you need a variant build of lighttpd that is stripped even further, then you have not shared why and have not shared the details of the constraints. Perhaps you should provide such details when asking on lighttpd forums: https://redmine.lighttpd.net/projects/lighttpd/boards (Please search the lighttpd forums for similar posts before posting.)
--- End Message ---
