Oh... you're right. I see what you're doing now.
1 Like
So how do you overcome me typing in these to URLs into my address bar:
https://kyouikulogistics.com/
https://www.kyouikulogistics.com/
I mean how do you correct the incorrect one?
1 Like
The only one of concern is this one:
https://kyouikulogistics.com/
1 Like
But they are both served from the exact same server block:
ServerName www.kyouikulogistics.com
ServerAlias kyouikulogistics.com
You have to say "only when" before do.
Or it will always do and loop d loop infinitely.
1 Like
You can either use a rewrite or two port 443 vhosts with the kyouikulogistics.com redirecting to www.kyouikulogistics.com.
2 Likes
Correct. Which justifies your rewrite. There's also the split vhost 443 way...
2 Likes
And then there is the .htaccess file way!
1 Like
I might be proverbially dragging my bumper behind the car but the site is working...seemingly without issue.
Where am I still incomplete?
1 Like
No, no, no. Never do that. Apache warns you to never use .htaccess when it can be avoided.
1 Like
BEER!BEER!BEER!BEER!BEER!BEER!BEER!BEER!
20 char limit
4 Likes
What kind of beer? Hoppy, lager, ???
1 Like
I like the split vHost myself, but certbot doesn't. 
2 Likes
SEO kind of dictates that you send all identic traffic to only one name.
Right now either name (both names) function fully on their own.
No bueno.
1 Like
This is known as a canonical address.
1 Like
Now there's a first ! ! ! ! ! ! !
1 Like
I see. At the moment the site simply hosts an application called Matomo used to track a different site on an entirely different server. Thus, I am basically the only one that accesses it. That may change though.
1 Like
You had be at "BEER"
Cheers 
1 Like
I know, right. Weird.
Much like not using rewrites... 
1 Like
@jlh, Perfection is not a requirement.
We're just... anal like that!
2 Likes