v3.3.1 MetadataProvider, metadataURL formatting question

[Peter Smith]

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, June 01, 2017 3:12 PM
To: Shib Users
Subject: RE: v3.3.1 MetadataProvider, metadataURL formatting question

> > I don't think so.
>
> I see https%3A//.  Is there a reason why %26 would fail?

I don't know that %3A actually works, it would depend on the library decoding it before trying to execute it. There's definitely no reason to encode a colon like that. More to the point, encoding the query string separator itself would change the meaning of the URL, so no, I don't think that would work unless it didn't need to be there to start with. If you want the URL it invokes to contain an ampersand, the XML parser needs to see it as one. If you want to encode it in hex, the syntax isn't percent-encoding in XML. & is a shorthand entity replacement.

-- Scott

-----

The 'https%A//' part was the URL given to me by the Vendor, unfortunately.  It is working now, however, with the '&' replacement suggested.  I now have the backing file created in my metadata directory and it is running.

PeterS

________________________________

UT Southwestern


Medical Center



The future of medicine, today.