W3C home > Mailing lists > Public > public-xg-webid@w3.org > October 2012

Re: WebID-ISSUE-64 (redirects): Redirects [WebID Spec]

From: Baptiste Lafontaine <baptiste33@gmail.com>
Date: Mon, 8 Oct 2012 22:07:01 +0200
Message-ID: <CANRJJJZV5QMPH9DWvKGc8n8Tc=c0AiycCJk4xQ8vJkdbsAPNXw@mail.gmail.com>
To: Henry Story <henry.story@bblfish.net>
Cc: WebID Incubator Group WG <public-xg-webid@w3.org>
2012/10/8 Henry Story <henry.story@bblfish.net>:
> On 8 Oct 2012, at 19:33, Baptiste Lafontaine <baptiste33@gmail.com> wrote:
>> I've read all this old topic but I face this issue while doing my
>> node.js implementation.
>> The current spec [1] says: "Add explanation for URI with redirect."
>> Should I follow all redirects ? What kinds of redirects makes the URL
>> of the query changed into the SparQL query ?
>> Please note that this is not a theoretical question and  I would
>> prefer a pragmatic answer.
>> [1] : http://www.w3.org/2005/Incubator/webid/spec/drafts/ED-webid-20111212/#verifying-the-webids
> I would say one should follow redirects of course. The question is what are the issues
> that may arise there. If an https url redirects to an http url then you must reduce the
> trust you have to trust towards that http resource, since that could have been man-in-the
> -middled.
> Otherwise I would follow as many redirects as seems cost effective. People who have too many
> redirects on their WebID should not be surprised if they have difficulty logging in. On the
> other hand servers that don't follow redirects at all will loose friends.
> What text do you think we should put there?

I would have say that the specification should be a little bit more
formal on this point by telling how many redirections should/must be
tested. This way WebID implementations may have more consistency and
prevent users from having WebIDs that work on some implementation and
does not on others.
In my opinion it's the same for the number of URIs from the certificate's SAN.

Another problem that I face : let say that bob has this into his
certificate SAN :

When reaching this URL, the VerificationAgent got a 301 (or 302) to

When using the SPARQL query defined in, should the
VerificationAgent test against https://bob.example/profile#me or
https://bob.somethingelse/profile#me ?


>> Thanks
>> Baptiste
> Social Web Architect
> http://bblfish.net/
Received on Monday, 8 October 2012 20:07:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:31 UTC