On Tue, Oct 30, 2012 at 6:23 AM, Lluís Batlle i Rossell <[email protected]>wrote:
> On Tue, Oct 30, 2012 at 06:17:05AM -0400, Richard Hipp wrote: > > Finally: Do you have any further ideas on how to defend a Fossil website > > against runs such as the two we observed on SQLite last night? > > This problem affects almost any web software, and I think that job is > delegated > to robots.txt. Isn't this approach good enough? Robots.txt only works over an entire domain. If your Fossil server is running as CGI within that domain, you can manually modify your robots.txt file to exclude all or part of the fossil URI space. But as that file is not under control of Fossil, you have to make this configuration yourself - Fossil cannot help you. This burden can become acute when you are managing many dozens or even hundreds of Fossil repositories. An automatic system is better. > And in the particular case of > the fossil standalone server, it could serve a robots.txt. > > How do programs like 'viewcvs' or 'viewsvn' deal with that? > > Regards, > Lluís. > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
