Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said Francis Daly on Sat, 29 Jun 2013 21:41:59 +0100: [I thought I had already responded to you but I cannot find the response. So if this is a repeat, I apologize. This does appear to be the problem.] > This says "run fossil http, and it should assume that any generated > sel

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said Richard Hipp on Sat, 29 Jun 2013 16:47:55 -0400: > Please bring up "fossil ui" locally, go to Admin/Settings and enable > test_env for me. This is now enabled, however, I believe Francis was able to point out the missing configuration option. I had apparently misunderstood the --

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Richard Hipp
On Sat, Jun 29, 2013 at 4:47 PM, Richard Hipp wrote: > > > On Sat, Jun 29, 2013 at 4:41 PM, Andy Bradford > wrote: > >> Thus said "Andy Bradford" on 29 Jun 2013 14:24:21 -0600: >> >> > Let me know if there's any additional information that would help. >> >> Not sure if this will help, but I set

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Richard Hipp
On Sat, Jun 29, 2013 at 4:41 PM, Andy Bradford wrote: > Thus said "Andy Bradford" on 29 Jun 2013 14:24:21 -0600: > > > Let me know if there's any additional information that would help. > > Not sure if this will help, but I setup two separate repositories using > the two methods I mentioned: > P

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Francis Daly
On Sat, Jun 29, 2013 at 01:57:39PM -0600, Andy Bradford wrote: Hi there, > My current iteration is using tcpserver (inetd replacement) and stunnel. > Stunnel's configuration is: > > cert = ./test.pem > exec = /tmp/fossil-src-20130618210923/fossil > execargs = fossil http /tmp/test.fossil This s

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said "Andy Bradford" on 29 Jun 2013 14:24:21 -0600: > Let me know if there's any additional information that would help. Not sure if this will help, but I setup two separate repositories using the two methods I mentioned: https://fossil1.bradfords.org:1231 Username: _fossil Password: ded6a

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said Richard Hipp on Sat, 29 Jun 2013 16:10:52 -0400: > Dunno if your problems are a Fossil bug or not. Please do > note, however, that you can access Fossil itself over https > (https://www.fossil-scm.org/) and the Fossil website is just a running > instance of Fossil

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said "Andy Bradford" on 29 Jun 2013 13:57:39 -0600: > > Redirect to Location: https://fossil:1621//login?g=/setup_config > > > > Which I assume my browser tries to fetch, but it clearly fails because > it returns to the Home page which wants me to click setup/config. I failed to include

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Richard Hipp
On Sat, Jun 29, 2013 at 3:57 PM, Andy Bradford wrote: > Hello, > > I'm trying to configure a secure fossil hosted repository using fossil > http. > My current iteration is using tcpserver (inetd replacement) and stunnel. > Stunnel's configuration is: > > cert = ./test.pem > exec = /tmp/fossi

Re: [fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Thus said "Andy Bradford" on 29 Jun 2013 13:57:39 -0600: > execargs = fossil http --baseurl https://fossil:1973/ /tmp/test.fossil Ignore the typo, I did have it correctly set to: execargs = fossil http --baseurl https://fossil:1621/ /tmp/test.fossil Don't let this distract from the original de

[fossil-users] Location http://https://domain bug?

2013-06-29 Thread Andy Bradford
Hello, I'm trying to configure a secure fossil hosted repository using fossil http. I've gone through various configurations, but each one has different problems. I would prefer to use SSH keys, but apparently fossil's client design doesn't lend itself well to ForceCommand SSH keys