Mobile app version of vmapp.org
Login or Join
Karen161

: Shifting from no-www to www and browsers' password storage I created a website having user-registration system and invited my friend to join it. I gave him the link of no-www version: http://mydomain.com

@Karen161

Posted in: #Browsers #Dns #NoWww

I created a website having user-registration system and invited my friend to join it. I gave him the link of no-www version: mydomain.com but now after reading this and this, I want to shift to mydomain.com.
But there's a problem. I saw that my browser is storing separate passwords for mydomain.com and mydomain.com. So in my friend's browser his password must have been stored for no-www. That means after I shift to www and next time he opens the login page, his browser wouldn't auto-fill the username and password fields and there will also be an extra entry (of no-www) in his browser's database of stored passwords.

Can this be avoided? Can I do something that will convey to browsers that mydomain.com and mydomain.com are the same website? I already have a CNAME record for www pointing to mydomain.com but it seems that search engines consider CNAME as alias but browsers consider them as different websites, I don't know why.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Karen161

1 Comments

Sorted by latest first Latest Oldest Best

 

@Nimeshi995

This is a limitation of the browser software and not that of your website, a browser will store passwords for an exact match URL which means if they visit the www site then that's where the password will be saved for, this is the same case for 'most' cookie based sessions.

Enforcing www

You can prevent this problem reoccurring by enforcing www in the URL address, this means no one will ever be able to visit the site without www and if they do it will redirect them to the correct address - meaning that saved passwords and sessions based cookies will be saved only for the correct URL preventing any problems.

There are many ways of how you can enforce www and this is one common solution using Apache with mod_rewrite:


SOURCE: What are the most commonly used and basic Apache htaccess redirects

Catch all and redirect non-www to www

You should opt to use mod_write for redirecting all requests for non
www versions of your site because the varible will catch page
names, so example.com/page1/ will automaticly redirect to
example.com/page1/.
mod_rewrite:

RewriteEngine On
RewriteCond %{HTTP_HOST} !^www. RewriteRule ^(.*)$ www.%{HTTP_HOST}/ [R=301,L]



People with saved passwords

You may find that you have to ask your site visits to clear their saved cookies and forms within the browser they are using should any further problems occur.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme