Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.7.0
-
None
Description
Despite the addition of a libcurl-based NetAccessor, which can handle https:// URLs, the XMLURL class prevents it from getting a chance to run when parsing because it hardcodes the allowable protocols.
This seems like a design flaw. If URL parsing really requires hardcoding specific protocols and ports, it should be a "known" protocol list, not a list that automatically blocks unknown protocols. If that isn't possible, then https should be added at a minimum.
It's not the XMLURL class' job to know what a NetAccessor can handle. If some kind of capability API is needed, then it should be added to the NetAccessor interface so the XMLURL class can ask it whether a given protocol will work.