[OpenID] Calling OpenID 2.0 editors (was RE:Problems withOpenID and TAG httpRange-14)

[Brendan Taylor]

On Fri, Mar 07, 2008 at 10:18:10AM -0800, Johnny Bufu wrote:
> Perhaps you should explain why your assumption (user-supplied id ==  
> claimed_id) should superceed the spec (condidering that without it  
> the spec stands).

This is *not* assumed. The user-supplied ID doesn't come into it at all.

The claim is that a 303 is a special case, and that ID normalization should
end when it receives one. (of course, the redirect still needs to be
followed for discovery)

Example:

http://example.org/me           301 redirect to http://example.org/bct
http://example.org/bct          303 redirect to http://example.org/about.html
http://example.org/about.html   301 redirect to http://example.org/about
http://example.org/about        200 OK with content that discovery can be
                                  performed on

if the user enters http://example.org/me or http://example.org/bct:
  currently:  claimed identifier = http://example.org/about
  proposed:   claimed identifier = http://example.org/bct

if the user enters http://example.org/about.html or http://example.org/about:
  both cases: claimed identifier = http://example.org/about
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20080307/95fe1999/attachment-0002.pgp>