(moderator please delete the missent post) Hello,
I just finished setting up Cherokee to replace thttpd. The motivating reason is that thttpd unpatched returns 'text/plain' for unknown extensions, which causes download corruptsions and problems for files which are not text. (fnord has the same misfeature). At first blush, Cherokee's behavior of simply not providing a Content-Type when it does not know what the content type is seems a most elegant behavior. ---- The largest problem I encountered when setting up Cherokee was interpreting the meaning of the Chroot option. When the chroot happens and how the variables are treated/handled in accordance with the chroot are the primay questions. Just the first would have saved me from stracing the program a fair amount. Exacerbating this is that a google search for cherkoee and chroot turns up this email: http://alobbs.com/pipermail/cherokee/2005-May/000722.html which suggests quite explicitly that the DocumentRoot should be redundant with the Chroot path, which i would not have expect and in fact is not correct (according to my experiences). I could possibly write a lousy (uncertain to be correct) first take on the chroot behavior based on my experiences and source readings. If this is useful, should I just edit the html, or is there a more upstream documentation form? ---- Secondarily, I enabled the UserDir feature for my users, and had some trouble figuring out how this would work inside a chroot. thttpd simply transforms /~foo into /users/foo if /users/foo exists, which seems safe and sane. cherokee tries to support apache style homedir access (which I think is a bad idea, but that is a design choice), and so does getpwent etc. Adding a fakey etc/password to the chroot works, but it is quite difficult to figure this out for the following reasons. 1) Access to the path http://host/~username returns an error, seemingly in all cases. http://host/~username/ works. Should I file a bug? 2) If UserDir is disabled, a path such as http://host/~username/dir will be silently transformed into an access to the path '/dir'. Surely the string should be passed along unchanged if it is not handled? ---- Thanks for what looks to be a great httpd. -josh _______________________________________________ Cherokee mailing list [email protected] http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
