<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [OpenID] RPs accepting https://
identifiers</title></head><body>
<div>>The obvious issue is that -- to my knowledge -- <a
href="https://openid.sun.com/user">https://openid.sun.com/user</a> != <a
href="http://openid.sun.com/user">http://openid.sun.com/user</a>.</div
>
<div><br></div>
<div>What if, for some crazy reason, a site actually *wants* to make
https://site.com/user a different page than http://site.com/user? For
instance, I could make a "Profile" page available via HTTP
that doesn't include any information I don't want to be captured in
transit - and then have *another* version of the same page, over
HTTPS, *with* that information.</div>
<div><br></div>
<div>Still the same user, though.</div>
<div><br></div>
<div>-Shade</div>
</body>
</html>