Webmasters Stack Exchange is a question and answer site for pro webmasters. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For a long time I've used OpenID delegation on my site:

http://example.org/ delegated to: http://example.openid-provider.com/, so I logged into OpenID-consuming sites using the former as ID.

Recently I added www. to my site's canonical domain so http://example.org/ now redirects to http://www.example.org/.

Should I be able to continue logging into existing OpenID accounts using http://example.org/?

StackExchange sites say "yes". I can use either URL.

At least one other doesn't recognize my existing account.

Who's "right" (per spec) and is there anything I can fix on my end?

share|improve this question

migrated from superuser.com Mar 8 '11 at 15:42

This question came from our site for computer enthusiasts and power users.

(Damn, I had to type this answer all over again because the web site design changed and locked the question. This is getting really frustrating and wasting a lot of time. And now, when I try to submit it, I get a blank web page with the message "Oh tin of pink meat / I ponder what you may be / Snout or ear or feet?")

How each person or organization sets up their systems is their choice. Traditionally the third-level "www." would provide the user with access to the web site as the "A" records in DNS specify the correct host (and many administrators would configure a tiny web server at whatever host is at "example.com" to re-direct the user to "www.example.com" to keep the load off).

These days many sites have one server running multiple daemons, so the need to differentiate these hosts isn't so important anymore.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.