DRE
Well-known member
I was doing some tests and noticed that sites with http:// first time to byte loads faster than sites with http://www.
Edit: Darn. Can't add poll.
Edit: Darn. Can't add poll.
I dunno...I tend to type: nameofsite + CTRL + Enter which automatically adds the www. and .com.without www. less typing other than that the same.
Are you typing in http://domain.com and it's redirecting to http://www.domain.com? That will take longer as it has to redirect.I was doing some tests and noticed that sites with http:// first time to byte loads faster than sites with http://www.
Edit: Darn. Can't add poll.
No. Looking at the results at webpagetest.org for several sites and saw that sites with www in front load slighty slowerAre you typing in http://domain.com and it's redirecting to http://www.domain.com? That will take longer as it has to redirect.
Well, just take a look at the Http headersThere shouldn't be any difference at all as far as I know unless it's redirecting as mentioned above.
GET /
Host: www.8thos.com
User-Agent: ...
GET /
Host: 8thos.com
User-Agent: ...
Unless you're comparing the same site (find one that doesn't redirect), you aren't comparing apples to apples.No. Looking at the results at webpagetest.org for several sites and saw that sites with www in front load slighty slower
xenforo.com doesn't use wwwYou should use www. in case you move your entire site to a CDN in the future, most don't work with non-www. That's why you see a lot of big sites use www.
xenforo.com doesn't use www
I have my site as http:// since our launch!
For the cookies issue we use .htaccess to redirect all users to http:// only link without the www.He has a point, though.
It makes using some third-party redundant hosting solutions more difficult, since they use a CNAME to point to their services. There's also other implications, such as cookies. In general, naked domains are a bad idea when used in a high availability environment, or when you're running a large number of services across several sub-domains. For your average forum, or those running their own server farms, it's not much of an issue.
RewriteCond %{HTTP_HOST} ^8thos\.com$ [NC]
RewriteRule ^(.*)$ http://www.8thos.com/$1 [R=301,L]
RewriteCond %{HTTP_HOST} !^8thos\.com$
RewriteRule ^(.*)$ http://8thos.com/$1 [R=301,L]
RewriteCond %{HTTP_HOST} ^8thos\.com$ [NC]
RewriteRule ^(.*)$ http://www.8thos.com/$1 [R=301,L]
RewriteCond %{HTTP_HOST} ^8thos\.com$ [NC]
RewriteRule ^(.*)$ http://www.8thos.com/$1 [R=301,L]
RewriteCond %{HTTP_HOST} ^www.yourdomain.com [NC]
RewriteRule ^(.*)$ http://yourdomain.com/$1 [L,R=301]
You are only using nginx as a reverse proxy. I'll take a look when I get to work this morningI want to ditch the www. and go straight to 8thos.com so I tried:
Code:RewriteCond %{HTTP_HOST} ^8thos\.com$ [NC] RewriteRule ^(.*)$ http://www.8thos.com/$1 [R=301,L]
Didn't work so I tried number 2: http://xenforo.com/community/threads/keep-logging-out-of-xf-with-chrome.22968/#post-286837
Code:RewriteCond %{HTTP_HOST} ^8thos\.com$ [NC] RewriteRule ^(.*)$ http://www.8thos.com/$1 [R=301,L]
Didn't work so I tried http://xenforo.com/community/threads/remove-www-from-urls.49207/#post-527144
Code:RewriteCond %{HTTP_HOST} ^www.yourdomain.com [NC] RewriteRule ^(.*)$ http://yourdomain.com/$1 [L,R=301]
Didn't work. @MattW is this not working because it has something to do with nginx? Even though I'm not using nginx for .htaccess and all...
We use essential cookies to make this site work, and optional cookies to enhance your experience.