marcoscaceres commented on this pull request.
> </p>
+ <ol class="algorithm">
+ <li>Let <var>url</var> be the result of running the <a>URL parser</a>
+ on <var>input</var>.
+ </li>
+ <li>If failure, <a>throw</a> a <code>TypeError</code> exception.
+ </li>
+ <li>If running <a>potentially trustworthy URL</a> with <var>url</var>
I'm still of the opinion that we should:
* restrict this to "https" (because Payment Manifest is the only serious consumer of the end points)
* Recommend "best practice" to developers to use paths and avoid query, fragments, username, and password.
That would mean that any URL with a `https://` scheme is a valid PMI-URL - and would make everything super simple.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-method-identifiers/pull/35#discussion_r113845968