Trailing Slash?

[Christopher E. Granade]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Calder wrote:
>>From the specs:
> 
> "* The delegate identity URL must be canonical. It will not be further
> processed by the consumer, so be sure it has the "http://" and
> trailing slash, if there's no path component."
> 
> On 10/17/05, Jason S Salaz <jason at zenenet.com> wrote:
>> A friend and I were trying our hardest to figure out why he could
>> comment to LiveJournal (and in general, use his domain with LiveJournal
>> as the server/delegate) by logging in via OpenID via his domain, and I
>> couldn't.
>>
>> We finally found out that I was missing a single / in the delegate URL.
>> (href="...livejournal.com" instead of href="...livejournal.com/").
>>
>> Is there a reason that this trailing slash is absolutely required?  And
>> why it (seeming unnecessarily :( ) causes so much grief?
>>
> 
In that case, perhaps append the following?


* The delegate identity URL must be canonical. It will not be further
  processed by the consumer, so be sure it has the "http://" and
  trailing slash, if there's no path component.
  NOTE: The consumer SHOULD append a trailing slash if appropriate, and
  if the login fails without the slash appended. Note also that a server
  SHOULD NOT recognize two identity URLs that differ only by a trailing
  slash.

- --Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDVApk0dXuuZr00J4RAqXEAKDIVTfO/53XJRFafo9yaAiAl5omdgCfWLY1
9DHoLqvK4APL90mKGbOjYKI=
=zmmu
-----END PGP SIGNATURE-----