www and non-www compatibility

Alanc

I've noticed that whichever canonical url option (www or non-www) is set as url in my config.php file

'url' => 'https://www.website/flarum',

the other option breaks font-awesome icons and most features such as logging in.

If I set it with www, browsing to flarum without www will render the forum unusable,
the same goes for browsing using www when the url is set without it.

Is there a way I can make both www and non-www load flarum completely, through a change in the config file or htaccess? Rather than using ModRewrite I'd like to just make both work.

inkdropmedia

Alanc You must have a LAMP server (apache2)?

I found that LEMP with Nginx is best for server setup. Then I used the server configuration file to point www to non-www, this is the best way. I never even had to touch the config.php file.

https://www.digitalocean.com/community/tutorials/how-to-redirect-www-to-non-www-with-nginx-on-ubuntu-14-04

FebriTriHarmoko

Alanc i think you need redirect site...
like if i try access www.website.com/flarum will be direct to website.com/flarum ...
i use this role ?

EbonJaeger

You could probably do a redirect using your web server, though this seems kind of hacky.

marlon

FebriTriHarmoko how did u do it? I'm in need of this solution too ? thanks

Alanc

I've used this rewrite in the htaccess file for now:

  RewriteCond %{HTTP_HOST} !^$
  RewriteCond %{HTTP_HOST} !^www\. [NC]
  RewriteCond %{HTTPS}s ^on(s)|
  RewriteRule ^ http%1://www.%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

It doesn't solve flarum only functioning using the url in the config file though, but it disallows access to a improperly functioning canonical url for users, so that's something. Non-www is forced to www.

FebriTriHarmoko

Alanc try this

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://yourdomain.com%{REQUEST_URI} [L,R=301,NC]
RewriteCond %{HTTP_HOST} ^www.yourdomain.com [NC]
RewriteRule (.*) https://yourdomain.com%{REQUEST_URI} [L,R=301,NC]

or if you use nginx, you can try this :

if ($host != "yourdomain.com") {
        return 301 https://yourdomain.com$request_uri;
}

i use this role, you can visit my flarum to try my setting xkomo(.)com/forum

Alanc

FebriTriHarmoko
Looking at your forum, it is non-www only, and adding www redirects you to a non-www URL.
This is the same kind of redirect as I used, but opposite. I have my flarum configured to be www, and non-www gets redirected (rewritten) to www.

For now, this is okay and it solves any visitor/user issues and I might as well just keep it as is, but the original issue that bothers me is that functions won't work and font awesome won't load using a canonical url that is not in the config.php file.

FebriTriHarmoko

marlon just follow this post FebriTriHarmoko

DTYlan

@Alanc If you want your users to be able to access your forum on both www and non-www, assuming that you've setup your virtual hosts to allow, you could use something a little like this:

File: config.php

'url' => ($_SERVER['HTTP_HOST'] == 'www.domain.com' ? 'https://www.domain.com' : 'https://domain.com'),

Not sure if there will be much of a security concern but seems solid when I have been testing it.

If the user logins into the forum on domain.com it will not log them into www.domain.com because of the session cookies only being accessed by the the original domain.

Davis

DTYlan this is a bad practice. Redirects from www->non-www or non-www->www should be done in nginx or Apache. It doesn’t matter which you choose but you need to pick one. Someone in this thread said it’s “hacky” but this couldn’t be further from the truth. Networking is outside the scope of an application.

clarkwinkelmann

For anybody trying to configure redirects (subdomains, paths, HTTPS, ...) in Apache here's a great resource: https://github.com/phanan/htaccess