Backport #9083
closed
Backport 9080 "Invalid relative URLs are not identified beforehand" to 3.14.z
Status:
CLOSED - CURRENTRELEASE
- Copied from Issue #9080: Invalid relative URLs are not identified beforehand added
- Sprint/Milestone set to 3.14.3
- Sprint changed from Sprint 100 to Sprint 101
- Status changed from NEW to ASSIGNED
- Assignee set to mdellweg
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
Validate absolute pathnames in remotes' URLs
Before this change, it was not possible to determine why did the synchronization fail when a user provided a seemingly valid URL. This commit also adds more relevant information to the error message.
Having set
ALLOWED_EXPORT_PATHS
to["/tmp", "/home/vagrant/test"]
, the following error messages are shown:backports #9080
fixes #9083
(cherry picked from commit d8cba5abdddbe2297e4b7c72571f08c55d88bcd4)