|Subject:||Re: [Taler] mint base URL subtleties|
|Date:||Sat, 12 Dec 2015 17:08:16 +0100|
On Dec 11, 2015 23:52, "Christian Grothoff" <address@hidden> wrote:
> Tricky. How do you know it should be http://, and not https://? I think
> if we don't do 1a, then at least we should default to https. Asking a
> mint to run https or fail on auto-completion is better than using http
> with a mint that does offer https.
Sure, I agree. A fancier mint could even probe for https and fall back to http.
> I'd say different base URL == different mint for the wallet. Otherwise,
> you don't know under which URL to interact with the mint, so that'd be
> bad. If the same mint operator uses the same mint keys under two
> different URLs, I see no problem with wallets that treat those mints as
> separate entities. The only point is that we need to track the mint by
> URL inside the wallet, instead of by the mint's master key. But that
> seems fine.
So "http://mint.example.com/" and "https://mint.example.com/" are treated as different mints.
This makes kinda sense, as long as the fancy version of the wallet offers to merge mints with different URLs but the same key.
|[Prev in Thread]||Current Thread||[Next in Thread]|