Actions
Backport #9083
closedBackport 9080 "Invalid relative URLs are not identified beforehand" to 3.14.z
Start date:
Due date:
% Done:
100%
Estimated time:
Triaged:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 101
Quarter:
Related issues
Updated by dalley over 3 years ago
- Copied from Issue #9080: Invalid relative URLs are not identified beforehand added
Updated by mdellweg over 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to mdellweg
Updated by pulpbot over 3 years ago
- Status changed from ASSIGNED to POST
Added by mdellweg over 3 years ago
Updated by mdellweg over 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|fc8d65688f4a423db4bbed8424d10a6a5ebcec6c.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
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)