Hello,
just tried those lines in the imscp/domain.tld.conf
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
But the domain is not always forwarded to https
Apache has been restarted
Maybe a suggestion?
Hello,
just tried those lines in the imscp/domain.tld.conf
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
But the domain is not always forwarded to https
Apache has been restarted
Maybe a suggestion?
Thanks for hint but I am already using this codeblock in the vhost conf.
it seems not to work after restarting apache.
Calling http://xxx.tld is not being redirected to https://xxx.tld
is there a reason why you don't use the .htaccess? i'm not sure but I guess the vhost.conf will be overwritten by i-mscp...
I also recommend writing changes into .htaccess.
BTW: In v1.3.x we'll provide HSTS feature, it's already committed into branch.
I guess the vhost.conf will be overwritten by i-mscp...
You're wrong here
imscp/domain.tld.conf allows the administrator to override directives from the main vhost. But for the http to https rewrite rule, it is not the right place because that file is included in both, the http vhost and ssl vhost.
Hi,
when I am right I couldn´t use an .htaccess because seafile is using fastcgi. So the forwarding should be done by apache configuration.
Is there another way to influence the forwarding?
Where would be the right place for this configuration as it is actually not possible to use seperate files for port 80 and 443?
I was wrong with my previous sentences. You can try something like:
in the /etc/apache2/imscp/<domain.conf> and then reload your apache configuration.
BTW: You can use the same statement in .htaccess (even if you use fastcgi).
Display More
I was wrong with my previous sentences. You can try something like:
in the /etc/apache2/imscp/<domain.conf> and then reload your apache configuration.
BTW: You can use the same statement in .htaccess (even if you use fastcgi).
Those lines did the trick - now it works.
Btw I was an idiot, those lines were additionally on the false position in the conf-files -.-
Thanks guys!