On Tue, Feb 10, 2015 at 10:50:24PM +0100, Gour wrote: > Francis Daly <fran...@daoine.org> writes:
Hi there, > > So presumably all that is needed is to use the fossil-cgi equivalent > > to fossil-http's "--https" argument. > > My site is set to use https-only, so to me it seems it's still the > original question how to move from HTTP to HTTPS scheme. I suggest the question is simpler: how do you use fossil-cgi behind a https server? I do not see the case covered on https://www.fossil-scm.org/xfer/doc/trunk/www/server.wiki or https://www.fossil-scm.org/xfer/doc/trunk/www/ssl.wiki other than an indication that it Just Works. (And since that server is running https, and is running as cgi, clearly it *does* Just Work. But also clearly, it does not Just Work for you. So either there's stale config in place, or some other difference in how things are set up.) It may be the case that https should be auto-noticed by fossil (by an environment variable, perhaps); if that is so, then you will want to identify why it fails in your case. It may be the case that you must configure fossil to know that it is behind a https server. "--https" was added to "fossil http" to handle it for that command. "baseurl" was added to "fossil cgi" if your local-part of the url is not what fossil would expect; that works for http and https, but not for the / url. I don't see an explicit configuration option available. I suspect that fossil Just Works if the cgi-server puts "HTTPS=on" into the environment; and I guess that your web server does not do that. Can you run a separate cgi script with content like == #!/bin/sh echo Content-Type: text/plain echo /bin/env == and see what comes out? (Unless someone who knows better can make a better suggestion, of course.) f -- Francis Daly fran...@daoine.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
