On 25 September 2017 at 13:59, Richard Hipp <[email protected]> wrote: > On 9/25/17, David Mason <[email protected]> wrote: > > I am trying things differently this year. I want to use one instance of > > fossil running proxied behind a firewall. I have the following in my > > Apache conf file: > > <Location /fossil> > > > > ProxyPass http://127.0.0.1:8081 > > > > ProxyPassReverse http://127.0.0.1:8081 > > > > SetOutputFilter proxy-html > > > > ProxyHTMLURLMap http://127.0.0.1:8081 /fossil > > > > </Location> > > > > RewriteRule ^/fossil$ /fossil/ [R] > > and the forward proxy works, except the resulting page doesn't have the > CSS > > and all the links are 127.0.0.1:8081 links instead of the right ones. > > > > How are you starting up the fossil server? Are you using the > --baseurl option so that Fossil knows how to construct URLs that point > to itself?
That solved it, thanks. I'm guessing I don't need the ProxyPassReverse and ProxyHTMLURLMap now. I can access the fossil web interface now at: https://cps506.scs.ryerson.ca/fossil/f2017/A-dmason_ryerson.ca using [email protected] for login, however if I try: fossil clone https://dmason%[email protected]/fossil/f2017/A-dmason_ryerson.ca.fossil <https://cps506.scs.ryerson.ca/fossil/f2017/A-dmason_ryerson.ca> foo.fossil it prompts for password, but then says it can't find it. Unfortunately the file system doesn't record access times, so I can't tell on the remote machine if the fossil file was read. Any ideas what I'm doing wrong? Thanks ../Dave
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
