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

Johnny Bufu johnny at sxip.com
Mon Mar 10 17:25:35 UTC 2008


On 6-Mar-08, at 11:44 AM, Noah Slater wrote:

> It's not an assumption, it's bordering on the absurd that I have  
> requote:
>
> RFC 2616 § 10.3.4:
>
>   The new uri is not a substitute reference for the originally  
> requested resource.

By your reasoning, if URL-1 303-redirects to URL-2, which in turn  
sends  a "welcome to URL-2" in the HTML body, a browser fetching  
URL-1 SHOULD (or MUST?):

- display URL-1 in the location bar
- parse the HTML content and replace every appearance of URL-2 with  
URL-1
- etc.

I believe this scenario is closer to the absurd than the current  
state of all major browsers to display URL-2, regardless which of the  
301/302/303/307 redirect types were followed.

If all browsers do this, I don't see why OpenID discovery can't.


Johnny





More information about the general mailing list