Trevor Power » www http://blog.trevorpower.com Software development and other thoughts Fri, 20 Aug 2010 07:33:51 +0000 http://wordpress.org/?v=2.8.6 en hourly 1 No WWW http://blog.trevorpower.com/index.php/no-www/ http://blog.trevorpower.com/index.php/no-www/#comments Fri, 07 Nov 2008 22:40:00 +0000 trevorpower http://trevorpower.com/blog/?p=20

I have never really thought about it before, but I hardly ever type ‘WWW’ into an address bar. Out of habit I skip this part of any URL. It has never caused me any problems till this week, for one of my own websites.

As I’ve said in an earlier post, I have added OpenID support to one of my websites. I used the DotNetOpenId library. This library made the development very easy and was up and running in no time on my development machine. But recently I have published the website to a live server and things haven’t been going that smoothly.

When a user provides an OpenID the url they entered must be stored on your server while the client is directed to the third party OpenID provider. This is to do with the fact that the url might redirect to another url/provider for authentication and in this case the original ulr/id may not come back when authenticated. To store the original url on the server I just bunged it into the session (I believe this is standard practice). However when I tested it on the live server I would always get an error because the session would be empty.
I then noticed that if from the error page, I try to log in again it would succeed. Eventually I figured out what was going on. The return address I was providing was of the form ‘www.mysite.com’ while I always typed ‘mysite.com’ when testing. Switching from the non ‘WWW’ version to the ‘WWW’ version of the url caused the session to be cleared.
Another problem is that when being authenticated by an OpenID provider, the relying party must provide a ‘realm’ that the user is authenticated for. The realm is basically the domain of the relying party website. The problem is that ‘www.mysite.com’ is not considered part of the ‘mysite.com’ realm.

This means that to keep things simple I had to decide which address I was going to use and redirect one to the other. The choice was made simple because no-www.org had some good arguments and the yes-www.org website was down (or maybe I forgot the www). 

Redirecting turned out to be easier than I thought (I didn’t need to contact hosting provider). I just added a ‘.htaccess‘ file to the root of my directory with the following lines 

RewriteEngine OnRewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]RewriteRule ^(.*)$ http://%1/$1 [R=301,L]

This tip I got from no-www.org.

]]> http://blog.trevorpower.com/index.php/no-www/feed/ 2