Bug #6450
closed
CollectionFinder misparses ALLOWED_PROTOCOLS
100%
Description
Bug #5847 introduced a patch to make the standard collection finder examine the ALLOWED_PROTOCOLS configuration setting to check that a particular protocol (or URI scheme) is in a permitted list.
The patch is incorrect in that it treats the configuration option as a space separated list rather than a comma-separated list.
This has the consequence that a particular protocol (e.g. "file") is disallowed despite being present in the whitelist.
Updated by Michael Kay 4 months ago
Unfortunately the unit tests for the configuration option make the same mistake - they supply a space-separated string.
Updated by Michael Kay 4 months ago
In fact the collection finder should not really be accessing the raw property and parsing it; rather it should check the scheme against the Configuration's ProtocolRestrictor, which will have parsed the property centrally.
Updated by Michael Kay 4 months ago
- Status changed from New to Resolved
- Fix Committed on Branch 12, trunk added
Updated by O'Neil Delpratt 4 months ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 12.5 added
Bug fix applied in the Saxon 12.5 Maintenance release.
Please register to edit this issue
.