[foaf-protocols] reference relations between 2 https endpoints/names, webid

Peter Williams pwilliams at rapattoni.com
Fri Jul 15 17:50:03 CEST 2011


https://bit.ly/oBSo5w

Folks in the linked data space generally want names and endpoints to be one and the same thing.

But, in foaf+ssl, what is the logic should the cert have a URI such as the above - a reference from one URI to another (courtesy of HTTP redirect).

That https URI becomes a link, under HTTP semantics (302). Which cert does the webid validator consider - that of the https bit.ly domain or the https endpoint/name that an agent at that address/name redirects to?

Is there an relation between the  2 (and generally n) (self-signed server) certs on a 2-party (n-party) https redirect chain?

Assume the self-signed certs of servers are the users cert, so that client certs and server certs share keying (and endpoint domains).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20110715/3fdf7949/attachment.htm 


More information about the foaf-protocols mailing list