Fossil SCM
remote `fossil clone` failed
a5fba652a688656…
· opened 17 years, 5 months ago
- Type
- Documentation
- Priority
- Zero
- Severity
- Cosmetic
- Resolution
- Not_A_Bug
- Subsystem
- —
- Created
- Oct. 16, 2008 1:01 p.m.
Command fossil clone http://www.fossil-scm.org/ myclone.fossil failed with the message: "fossil: connection to server failed"
Also I try to start thttpd-server and clone my local repo but fossil failed with the same error. thttpd log says:
127.0.0.1 - - [16/Oct/2008:17:00:29 +0400] "POST /home/user/work/misc/test/test.fossil/xfer HTTP/1.1" 403 0 "" "Fossil/[3d62a9fb39]"
stephan added on 2008-12-13 09:05:15:
HTTP code 403 is "forbidden", which makes it sound like you're trying to clone the fossil repository database file directly. When cloning over the net you need to give the URL of either a standalone RUNNING instance of the fossil web server OR a CGI script which runs the fossil app from an existing webserver (e.g. Apache). For example, here's a CGI script for one of my repos:
me@host [~/www.fossil/repos/pegc]# cat index.cgi
!/home/me/bin/fossil
repository: /home/me/fossil/pegc.fsl
And the URL for that repo is:
http://fossil.wanderinghorse.net/repos/pegc/index.cgi
For that to work i had to add a .htaccess file to my top-most directory (so i can run .cgi files in any subdirs):
me@host [~/www.fossil]# cat .htaccess Options +ExecCGI +Indexes
doesn't work on my hoster :( AddHandler cgi-script .html
DirectoryIndex index.cgi index.php index.html
anonymous added on 2010-10-05 10:49:24: I fell into this trap too. Could we review the (otherwise excellent) docs to make sure they're clear on this matter?