This should be applied evenly to any of the redirect scenarios. OpenID
specifies following redirects to find the final URI, while Yadis (as specified
in XRI Resolution 2.0) calls to obey all HTTP rules (which includes redirects
as well).
EHL
-Original Message-
From: [EMAIL PROTECTED] [
> This is what I was getting at- it'd be good to give users an identical
> experience when they sign into various OpenID-enabled apps.
Just to be clear, this is not an interop issue. This is a matter of
drawing the line between what is sane and what is not. For
pathological cases (e.g., excess
Aside from the depth issue, is there any distinction drawn between 301
(permanent) or 302 (temporary) redirects in the OpenID specification?
David Recordon wrote:
Hi Marv,
This has never been specified as a relying party could choose to
follow as many redirects as it wishes. Maybe there sho
David Recordon wrote:
> Hi Marv,
> This has never been specified as a relying party could choose to
> follow as many redirects as it wishes. Maybe there should be a hard
> line drawn though from an interoperability side?
This is what I was getting at- it'd be good to give users an identical
exp
Hi Marv,
This has never been specified as a relying party could choose to
follow as many redirects as it wishes. Maybe there should be a hard
line drawn though from an interoperability side?
--David
On Feb 17, 2008, at 3:06 PM, SignpostMarv Martin wrote:
> Was talking with keturn in #openid
