I have setup fossil to serve repositories using inetd (xinetd in my case) as per http://fossil-scm.org/index.html/doc/tip/www/server.wiki
Lets say http://example.com:8585 is serving from /home/fossil/repos and there are two fossil files in there: repo1.fossil repo.name.with.periods.fossil Then: $ fossil clone http://example.com:8585/repo1 repo1.fossil [OK] $ fossil clone http://example.com:8585/repo.name.with.periods repo2.fossil fossil: server says: 404 not found ... At the same time if, on the server, we do 'fossil server', instead of serving using 'fossil http' + inetd: $ fossil server --port 8686 /home/fossil/repos/repo.name.with.periods.fossil Then the earlier clone succeeds: $ fossil clone http://example.com:8686/repo.name.with.periods repo2.fossil [NOW OK] Is this a bug? -Nick
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
