[OpenID] URL normalization issues

[John Panzer]

This also seems relevant:

http://www.intertwingly.net/blog/2004/07/31/URI-Equivalence

Here's another fun one (actually got bit by this last month) which is 
apparently normalized client side in browsers:

http://example.org/foo/../  vs.  http://example.org/

In general I think there is a server best practice here which involves 
returning 200 OK only for one canonical version of a URL, and 301's or 
404's for any other variants.  And a best practice for clients is to not 
rely on the Java URI class for equivalence checking :).

-John

Sutra Zhou wrote:
> Follow redirects,
> and  in HTTP 301 case(http://example.com/old redirect to 
> http://example.com/new) 
> net.openid.discovery.Identifier.getIdentifier() should return 
> http://example.com/new instead of http://example.com/old.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> general mailing list
> general at openid.net
> http://openid.net/mailman/listinfo/general
>   


-- 
Abstractioneer <http://feeds.feedburner.com/aol/SzHO>John Panzer
System Architect
http://abstractioneer.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070323/b0a7b0a1/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: SzHO.gif
Type: image/gif
Size: 8100 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070323/b0a7b0a1/attachment-0002.gif>