Project

Profile

Help

Bug #6450

closed

CollectionFinder misparses ALLOWED_PROTOCOLS

Added by Michael Kay 6 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Configuration
Sprint/Milestone:
-
Start date:
2024-06-11
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
11, 12, trunk
Fix Committed on Branch:
12, trunk
Fixed in Maintenance Release:
Platforms:
.NET, Java

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.

Actions #1

Updated by Michael Kay 6 months ago

Unfortunately the unit tests for the configuration option make the same mistake - they supply a space-separated string.

Actions #2

Updated by Michael Kay 6 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.

Actions #3

Updated by Michael Kay 6 months ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 12, trunk added
Actions #4

Updated by O'Neil Delpratt 5 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

Also available in: Atom PDF