On Fri, Apr 22, 2011 at 3:47 AM, Richard Hipp <d...@sqlite.org> wrote:
> It never occurred to me to make the built-in server of Fossil have the > ability of serve separate files. I figured that anybody who wanted to do > that would use a "real" web server like Apache or Nginx or even something > like the "althttpd" server shown above. > Hosting "real" files over fossil-cgi is also slightly problematic because we have to manually construct full hyperlinks (including the protocol and domain name). We can't use e.g. [/download/foo.zip] in a wiki page because the path won't resolve properly for that use case. It resolves to /path/to/cgi-script.cgi/download/foo.zip. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
