What happens if you set base_url without trailing slash? e.g. " https://foobar.com:10443";
On Wed, Jul 24, 2013 at 4:55 PM, Eric Rubin-Smith <[email protected]> wrote: > I think the point here is that with a baseurl of " > https://foobar.com:10443/";, certain links exposed by the fossil HTML > generators wind up pointing my browser to e.g. " > https://foobar.com:10443//page_name";, with two slashes after the port > number. And fossil's name resolution system does not squash the two > slashes -- there's a paged named "page_name" but none named "/page_name". > > Am I doing something wrong with my configs, or is a code change warranted? > > > On Tue, Jul 23, 2013 at 10:30 PM, Eric Rubin-Smith <[email protected]>wrote: > >> Yes, that works for the test case. But I think I'll need --baseurl for >> when I put fossil behind an SSL-terminating reverse proxy and want to >> access it using the company FQDN. >> >> >> On Tue, Jul 23, 2013 at 10:22 PM, Andy Bradford < >> [email protected]> wrote: >> >>> Thus said Eric Rubin-Smith on Tue, 23 Jul 2013 22:02:11 -0400: >>> >>> > /usr/local/bin/fossil server /home/fossil/myrepo.fossil --th-trace -P >>> 10080 >>> > --baseurl http://localhost:10080/ >>> >>> Try removing the --baseurl option. >>> >>> It works for me when I do: >>> >>> fossil server /tmp/test.fossil >>> >>> ssh -L 10080:localhost:10080 remote >>> >>> Andy >>> -- >>> TAI64 timestamp: 4000000051ef3a90 >>> >>> >>> >> > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
