Re: [w3c/webpayments-method-identifiers] Identifier equivalence does not handle failure (#8) from Anne van Kesteren on 2016-09-13 (public-webpayments-specs@w3.org from September 2016)

From: Anne van Kesteren <notifications@github.com>
Date: Tue, 13 Sep 2016 05:13:22 -0700
To: w3c/webpayments-method-identifiers <webpayments-method-identifiers@noreply.github.com>
Cc: webpayments-specs <public-webpayments-specs@w3.org>, Comment <comment@noreply.github.com>
Message-ID: <w3c/webpayments-method-identifiers/issues/8/246662193@github.com>

But you need to define that. Otherwise some implementations end up treating `https://example`, `https://example/`, `https://example:443/`, and `https://EXAMPLE/` as identical, whereas others don't.

-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments-method-identifiers/issues/8#issuecomment-246662193

Received on Tuesday, 13 September 2016 12:13:54 UTC