Solve DirectAdmin issues

  1. Listing in DirectAdmin of domains and their PHP version would help.
    Eg: grep php /usr/local/directadmin/data/users/*/domains/*.conf |more
  2. Since version 1.57.0: The ‘Force Redirect’ for www. or not, needs a change to work until after security headers.
    The old choice can be correctly included in this way:
    – None (default) / Plus www / No www;
    – Early rewrite (old) / Late 301 redirect / Late 302 redirect;
    For the long-standing redirects functionality placed at the bottom of .htaccess, consider putting them after httpd.
    Workaround: Force Redirect ‘none’. In the redirects functionality www. redirects to with no www.
    Current explanation by DirectAdmin:

Defect reproduction text issue no. 2: rewrites to

Security headers, such as HSTS, are required to work with the first domain name over HTTPS. So the rewriting called “Force Redirect” combined with the early rewriting to HTTPS has to be built in differently.


Please redesign the order; I think many scenarios are catched this way:
step 1. rewrite from HTTP to HTTPS by GUI DirectAdmin (works before reaching .htaccess)
step 2a. security headers in .htaccess, if .htaccess is read
step 2b. security headers on webserver / httpd level
step 3. 301 / 302 redirect by GUI DirectAdmin in order to achieve plus or no www.
(after any security header on webserver / httpd level)

– Own code is unnecessary if GUI DirectAdmin guarantees to do the same;
– ‘Note that we consider HTTPS as a requirement for these security options.’.
Can be textual: ‘Security headers are required to work with the first domain name over HTTPS.’