- From: Jürgen Jakobitsch <j.jakobitsch@semantic-web.at>
- Date: Fri, 06 Jan 2012 00:31:02 +0100 (CET)
- To: Henry Story <henry.story@bblfish.net>
- Cc: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org>
hi henry, http://2sea.org/sea.jsp#j still fails with "keys in profile don't match key in certificate for http://2sea.org/sea.jsp#j". i have taken all whitespaces out, pyRdfa and appspot extraction says it looks good. i have also deleted the compiled jsp from tomcat's work directory to be sure you get the latest version without whitespaces and newlines in key. uri also works with openlink [1] and webidrealm. maybe you find something in your logs... i recommend feeding the uri to your rdfa parser and check what happens with the hexBinary. what rdfa parser do you use? note : http://eastghost.org/ghost.ttl#j => success [1] http://id.myopenlink.net/ods/webid_demo.html wkr j ----- Original Message ----- From: "Henry Story" <henry.story@bblfish.net> To: "public-xg-webid@w3.org XG" <public-xg-webid@w3.org> Sent: Friday, January 6, 2012 12:16:16 AM Subject: fixed https://foafssl.org/test/WebId I fixed the test end point at https://foafssl.org/test/WebId The issue was (as I thought) that foafssl.org was not updating its caches on failure of a WebID authentication. This meant that people who tried to connect once with a broken foaf file, would not be able to re-connect later with a good one. It should work now. Henry Social Web Architect http://bblfish.net/ -- | Jürgen Jakobitsch, | Software Developer | Semantic Web Company GmbH | Mariahilfer Straße 70 / Neubaugasse 1, Top 8 | A - 1070 Wien, Austria | Mob +43 676 62 12 710 | Fax +43.1.402 12 35 - 22 COMPANY INFORMATION | http://www.semantic-web.at/ PERSONAL INFORMATION | web : http://www.turnguard.com | foaf : http://www.turnguard.com/turnguard | skype : jakobitsch-punkt
Received on Thursday, 5 January 2012 23:34:15 UTC