Director fails to find `/pnfs` as prefix for `/pnfs/fnal.gov/...` object requests

[jhiemstrawisc]

Pelican Service:

• [ ] Client
• [ ] Plugin
• [ ] Registry
• [ ] Director
• [ ] Origin
• [ ] Cache
• [ ] Other (please give the detail)

Describe the bug When requesting a redirect from the Director for an object under /pnfs/fnal.gov/..., the director responds that there are no known matching prefixes, despite the fact that requests for /pnfs/... generally get the correct redirect. I've narrowed down the issue to the inclusion of the . in fnal.gov as part of the object path, but am still looking as to where this is being improperly handled by the director.

To Reproduce curl -v https://osdf-director.osg-htc.org/api/v1.0/director/origin/pnfs/fnal.gov/foo yields no redirect, whereas curl -v https://osdf-director.osg-htc.org/api/v1.0/director/origin/pnfs/foo does.

Expected behavior Requests for /pnfs/fnal.gov/foo should match with the origin exporting the /pnfs namespace

[jhiemstrawisc]

This turned out to be an issue with the difference in registrations between Pelican and Topology. As such, there's no change to be made here.