On Feb 1, 2010, at 9:10 AM, Jeremy Cowgar wrote: > wrote: >>>> I wish it served a page at the root that listed all hosted >>>> repositories. Would it be a security problem to do that? >>> >>> I thought it would be. Perhaps not in every instance, but I can >>> envisions scenarios where a user would not want that listing to >>> appear. >> >> The standard solution of web servers is to see if index.html exists >> in the >> directory and if so, serve that page; if not a 404 results. Many >> servers >> have the option to do a listing, but that is just that: an option. >> > > Hm, an index.html is a great suggestion! (sent mine before reading > this one).
If Fossil returns the index.html file, then before long you also want to return various images and CSS files that index.html references. And then people will want a way to return favicon.ico. And robots.txt. And then you will need a way to customize the mimetypes of the various files. Already here is a feature request to allow the repositories to have extensions other than ".fossil". How long before people want the ability to handle multiple domains using the HTTP_HOST property of the HTTP header? I do *not* want to turn Fossil into a general-purpose web server and replacement for Apache. That is not its purpose. We have to draw the line somewhere, and I propose to draw the line here. D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
