- From: Henry Story <henry.story@bblfish.net>
- Date: Tue, 19 Apr 2011 23:22:06 +0200
- To: WebID Incubator Group WG <public-xg-webid@w3.org>
>
> Okay then — excuse my ignorance — please outline to me, how _exactly_ it will work when:
>
> a) Grandma has a "WebID" certificate containing only a SAN with a mailto: URI
>
> and
>
> b) the server (with a "Log in with your WebID!” button) only supports http: and https: URIs
>
> What *exactly* do you think should happen in this instance?
>
What a great server SHOULD do is:
1. presents the lady with an exception message in a nice http page, explaining what went wrong
2. on next connection the TLS layer should throw one of the exceptions for certificate errors
I wrote a little one page java server that does this
https://github.com/bblfish/TLS_test
It turns out Safari does (did) properly react to this, so that it is possible to log out from Safari in TLS.
I think I reported a bug in chromium, though perhaps a new one should be opened there that gets to this issue more particularly.
http://code.google.com/p/chromium/issues/detail?id=54405
It would be useful to test the other browsers on this.
Henry
Social Web Architect
http://bblfish.net/
Received on Tuesday, 19 April 2011 21:22:37 UTC