On Tue, 08 Oct 2013 15:26:17 +0200, Richard Hipp <d...@sqlite.org> wrote:
On Tue, Oct 8, 2013 at 9:15 AM, j. van den hoff
<veedeeh...@googlemail.com>wrote:
On Tue, 08 Oct 2013 14:50:24 +0200, Stephan Beal <sgb...@googlemail.com>
wrote:
I suspect for most users it will seem natural to choose a descriptive
free text project name and then the zipfile name ends up as something
like
(this is a real world example...):
sd+--+a+drop-in+replacement+**for+`cd'-ae9ca63258d41bda.zip
which is not especially inviting to keep this as the final name of the
unpacked archive dir...
I checked in a change that encodes things in the admittedly ugly way. It
is ugly but it does work, pending a final resolution of the problem.
I further observed that having "/" characters in the project name was
never
a problem for Firefox, on which I do most of my testing. Which browser
was
the issue originally observed on?
opera (but I think I've tried with chrome, too). and the problem occurred
when testing access to a "cgi-repo" on a web-server (as explained in my
original post). I've just tried to reproduce the problem locally (when
using `fossil ui'): in this case I see something different, namely that
everything in the project name up to and including the (in this case
single) `/' is omitted from the generated zipfile name, e.g.,
"something/or-other" becomes "or-other-0253aa7c17e75b5a.zip"
(which works, of course, but still is not preferable over a name just
consisting of the sha1 has in my view)
but no problem related to "invalid URL" as previously with the "cgi-repo".
if need be I can of course test it with the "cgi-repo" again. just let me
know
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
