On Tue, 27 Dec 2011 19:36:38 -0500 Richard Hipp <[email protected]> wrote:
> Fossil expects (in accordance with the CGI spec) the HTTPS environment > variable to be set if it is run from CGI and HTTPS is used instead of > HTTP. It will when automatically make all the hyperlinks also use > HTTPS. Ok that makes sense. I might be able to trick it into working now. > Are you aware of althttpd? A single source file. Documentation > consists of a comment at the beginning of the file ( > http://www.sqlite.org/docsrc/artifact/14c9965da19?ln=2-62). This is > this webserver that handles the Fossil website (and also the SQLite > website). It easily handles 300K requests/day on a 1/24th slice of a > single server (at Linode.com) without the load average ever going > about 5%. That's so funny (in an awesome way). Will it do SSL/TLS? I'm on linode also. My thinking is that I have 1 ip and would like to stick to the standard ports 80 and 443, while mixing static content, fossil, and possibly other. Some public, some private, thus the ssl for the login security. I suppose the alternative would be to just go ahead and let fossil run in its own server instance with ssl enabled on another port. There just seems to be so many organizations that filter out web content on odd ball ports. Or of course the dreaded apache. btw, I'm the guy from your audience at SELF, that was asking way too many questions. Just a few more days left in my goal to migrate some repos by the end of the year. -- www.thomasstover.com _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
