Hello, on Tuesday 27 May 2014 at 15:46, Richard Hipp wrote: > On Tue, May 27, 2014 at 3:43 PM, Warren Young <war...@etr-usa.com> wrote: > > > I had a file called README-Visual-C++.txt in one of my repositories and > > wanted to link to the tip version of it from an outside web page. I > > discovered the "doc URL" feature in Fossil, but it didn't work with that > > file. Apparently there's some kind of data sanitization going on here that > > turns the +'s into spaces. > > > > I say "had" because I just renamed it to README-Visual-Studio.txt and > > moved on. Perhaps someone wants to fix this in Fossil, though. > > > > I think that's an HTTP thing. In a URL, spaces are encoded as "+". So > fossil is doing the right thing in converting "+" characters in the URL > into spaces. > > If the filename really does contain "+" symbols, then the URL should have > "%2b" for each plus. ex: > http://localhost/doc/trunk/README-Visual-C%2b%2b.txt
In mohawk (tiny) webserver project we encountered the same kind of problem, and discovered in the process that major webserver (like apache, nginx and lighttpd, though I don't remember exactly which ones) fall back on not decoding '+' when providing files from disk. I can understand how one could see value in following the most common behavior even when it's technically not the right thing to do. Hoping this helps, Natacha Porté
pgpISegVxdCcY.pgp
Description: PGP signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
