www.linux.org and linux.org sign in

[f33dm3bits]

Because of some stupid mistake I made I had to sign in into all the websites I am normally signed in again. However what I have noticed before and this time again is the forums have two domains where it is active on. The main domain "linux.org" and the sub-domain "www.linux.org" to access both I have to sign into each individually. Would it possible to have it so that if you are signed into one that you are signed into both? Or just make a decision to have one of them being the actual login domain and the other an alias domain to then have the alias redirecting to the main domain. That way you only have to sign in once. I've noted that emails you got for a new topic notification use www.linux.org so then it might be just better to have "www.linux.org" to be the main domain and "linux.org" the alias domain?

 

[sphen]

I noticed the www.linux.org and linux.org issue when a while ago, but didn't say anything. I assumed a minor website misconfiguration, no big deal.

I looked, and I currently have cookies for both linux.org and www.linux.org. The login cookies are different and expire on slightly different dates in May 2024. It makes me think that they are good for a year, but the web server could ignore the expiration date and force a login based on creation date.

I wonder whether it would be easier to login on both and then both would work. That is the way it works for me.

One related note:
On my old Safari browser, typing "linux.org" automatically redirects to "https://www.linux.org". To go to the actual "linux.org", I must type the full "https://linux.org". I must have done that last month.

 

[KGIII]

Would it possible to have it so that if you are signed into one that you are signed into both?

Cookies don't like to work on multiple sub-domains. I believe you can make it work, but my solution is just to redirect all wsw.example.tld to example.tld.

For example, try: https://www.linux-tips.us

 

[f33dm3bits]

Cookies don't like to work on multiple sub-domains. I believe you can make it work, but my solution is just to redirect all wsw.example.tld to example.tld.

For example, try: https://www.linux-tips.us

That's why I would think it would be better to use www.linux.org as the main domain since the links in the emails point to that and make linux.org the alias domain. Then in the webserver configure it that when someone types in linux.org they get automatically redirected to linux.org that way you only have to worry about login cookies for one domain.

 

[KGIII]

Then in the webserver configure it that when someone types in linux.org they get automatically redirected to linux.org that way you only have to worry about login cookies for one domain.

It's just as easy to redirect traffic to www.domain.tld.

Add this to the .htaccess:

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

 

[f33dm3bits]

It's just as easy to redirect traffic to www.domain.tld.

Add this to the .htaccess:

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

Yeah something like that would be nice for linux.org -> www.linux.org

 

[KGIII]

Yeah something like that would be nice for linux.org -> www.linux.org

I have a strong preference for example.tld over www.example.tld, because www is just a subdomain and not special in any way. The www is no different than foo.example.tld or bar.example.tld. So, the root domain is example.tld which is why I forward traffic there, resolving this issue.

But...

It's not a hill I'm going to die on. I followed someone's link recently so I'm using the www subdomain right as I type this. I haven't bothered to correct it. It's just not that important to me, so I don't mind if it's 'backward'.