[Duplicity-tracker] [patch #6298] URI unquoting patch for FTP backend

[Peter Schuller]

Follow-up Comment #5, patch #6298 (project duplicity):

The standard - as in the URL RFC?

If so, should this apply to other backends as well?

This is a common problem with the 'strict' URL form rather than scp style
paths, and is a problem exhibited by other backends too. It took me some tries
to realized that two slashes was the way to do it with e.g. the rsync and scp
backends.

Do we believe the correct fix would be to apply this logic to all backends
with a host component (and presumably documenting it in the process)?

My personal reservation is that while perhaps standards-compliant, it is
unfortunately very obnoxious in shell scripting to replace the first slash of
a remote host path with a %2F; and this is a pretty common use case (at least
for the ssh backend).


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?6298>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/