Update redirect to Sentora login to an error page if a sub domain does not exist

[TGates]

Currently, if a sub domain of your main domain (the one that you use for your Sentora login sub domain) does not exist on the server, all requests get sent to the Sentora login.

I myself do not like this and have added custom code to prevent it. (Shows a generic 404 page)

Two solutions:

1. Redirects to 404 if sub domain does not exist or direct IP access is used.
   - This makes doing this redirect controversial since beta testers and people who prefer to access the Sentora login via IP will no longer be able to do so.
   
2. Redirects to 404 if sub domain does not exist and allows direct IP access
   

Should we add one of these to Sentora as a default installation feature?

Place your vote and comment below about your ideas.

[kevwebbie]

I've been logging in using the server ip and like it. It also tells me if sentora is installed properly without having to change dns settings.

[Me.B]

Should be under construction page or error 503.

[TGates]

I've been logging in using the server ip and like it. It also tells me if sentora is installed properly without having to change dns settings.

kevwebbie:
Note: The code for this already exists in the /etc/sentora/panel/.htaccess file:

Code:

# Optionally you can uncomment the below line and configure your domain to only allow access from the FQDN.

#RewriteCond

%{SERVER_NAME} !^sentora\.domain\.com$

#RewriteRule

^ - [F]

The proposal is to disable IP access by default allowing the server owner to enable IP access if they wish.

Should be under construction page or error 503.

503?

503 Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.

Under construction wouldn't be correct either if the resource (or page) doesn't exist, then it's a 404 not found.