[SVN-2028] Separate path functions from URL functions

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: all
• Fix Version/s: 1.7.0
• Component/s: libsvn_subr
• Assignee: C. Michael Pilato
• Reporter: Greg Hudson
• Created: 29/Aug/04 14:40
• Updated: 27/Oct/18 16:29
• Resolved: 04/May/11 22:27

Description

A number of svn_path functions are documented as accepting URLs in particular
positions.  This practice can lead to trouble if a caller assumes without 
checking that what it has is a path; for instance, if you
svn_path_canonicalize() a URL and then pass it to svn_path_dirname(), what
should happen if you reach the "http://hostname" part of the URL?

In 2.0, we should have separate functions for operating on paths and URLs, and a
third set for operating on "targets" which might be either (e.g.
svn_target_is_url to distinguish between path targets and URL targets).  Then if
you canonicalize a URL as a path, what you will get back is a canonicalized path
(e.g. "http:/hostname/path"), not a URL, and the behavior of svn_path_dirname
and friends are well-specified.

Issue Links

• blocks: SVN-1711 Many svn_path functions cannot handle Windows paths
• blocks: SVN-3601 ra_serf gets PROPFIND failure on certain non-ASCII paths
• blocks: SVN-2490 Subversion is too sensitive to particulars of URL encoding in working copy
• blocks: SVN-2676 Add svn_path_from_user_input() to the public API.
• blocks: SVN-1880 API improvements for 2.0 (meta issue)
• is depended upon by: SVN-1711 Many svn_path functions cannot handle Windows paths
• is depended upon by: SVN-3601 ra_serf gets PROPFIND failure on certain non-ASCII paths
• is depended upon by: SVN-2490 Subversion is too sensitive to particulars of URL encoding in working copy
• is depended upon by: SVN-2676 Add svn_path_from_user_input() to the public API.
• is depended upon by: SVN-1880 API improvements for 2.0 (meta issue)