Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display message when not adding www redirection #232

Open
kirtangajjar opened this issue Nov 26, 2018 · 2 comments
Open

Display message when not adding www redirection #232

kirtangajjar opened this issue Nov 26, 2018 · 2 comments
Labels
good first issue Good for newcomers

Comments

@kirtangajjar
Copy link
Contributor

kirtangajjar commented Nov 26, 2018

EasyEngine adds www redirections(www.example.com -> example.com or vice-versa) only if it finds that domain with www is pointed to the server. The reason for doing so is that to add https redirect from www.example.com -> example.com, we need a cert that is valid for both domains www.example.com and example.com. And to get that certificate, we need to ensure www is pointed to the server.

This leads to confusion among users who find that sometimes the redirection file is added, while sometimes it is not - https://community.easyengine.io/t/ee-site-create-503-service-temporarily-unavailable/12032

Solution to this issue is:

  1. Always add HTTP www redirection
  2. If the site has SSL and www domain is pointed, add https www redirection
  3. If the site has SSL and www domain is not pointed, show a message on the user's screen that https redirection is not added as the domain is not pointed. Also, add a similar message as comment in the redirection config file.
@kirtangajjar kirtangajjar transferred this issue from EasyEngine/easyengine Nov 26, 2018
@kirtangajjar kirtangajjar added the good first issue Good for newcomers label Jul 23, 2020
@gingerbeardman
Copy link

This would be welcome

@gingerbeardman
Copy link

gingerbeardman commented Apr 25, 2022

So the reason I'm not seeing redirection is that I am not set correctly at a DNS level?

If that's the case could the specifics of the problem be displayed in the message?

Example, rather than a generic message

"www is not pointed at this server"

it would say

"www is pointing to example.com bit should be pointing to 12.34.56.78"

This would allow me to quickly resolve the problem with no further troubleshooting needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants