On 4/22/15, Abilio Marques <abili...@gmail.com> wrote: > Hi, > > I keep the main storage for my repos in a directory called ~/.fossilrepos . > I've been using for a few years now: > > fossil server ~/.fossilrepos (with nohup) > > And it works perfectly. Yet, today I was trying to use the --files option. > I first made an experiment with something like: > > fossil server --files '*.txt' ~/tmp > > And it correctly served to me a file called hello.txt. Yet, when I try to > browse to a txt file inside the real directory, using: > > fossil server --files '*.txt' ~/.fossilrepos > > I get a not found. So I made a quick test and renamed the directory to: > fossilrepos (without the dot). Then restarted, and it serves the *.txt > files just fine. It seems it doesn't like the dot in the repo directory. > > Is that normal behaviour? >
Yes. There are restrictions on the file and directories names used by the web-server. These restrictions are designed to enhance security, and prevent attacks that consist of sending unusual URIs into the web-server with the aim of unauthorized content. https://www.fossil-scm.org/fossil/artifact/41d452b2fa?ln=1508-1526 -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
