You really only have one option at the moment and that is to pay for a
wild card certificate which will do this {lets encrypt doesn't allow you
yet}
It will probably set you back something like 100$ a year....
o/w you will need to set your redirects up from xxx.**** to https://
individually and have a catch all that redirects the rest of the http
request to a single https domain...
On 2017-05-15 05:03 PM, Torge Riedel wrote:
Hi,
I'm using Apache 2.2 and currently have the following configuration
files:
00-default -> redirect non-https-URLs to https-URLs
00-default-ssl -> default configuration for
https://mydomain.de and https://www.mydomain.de
Then several files
20-sub.mydomain.de -> configuration for https://sub.mydomain.de
So what I want to do is if a user browses to my domain with an
unconfigured sub domain, he is redirected to lets say
https://www.mydomain.de
Reason: Currently he gets a certificate error, cause cert
(letsencrypt) is only valid https://mydomain.de and
https://www.mydomain.de
Any hints?
Thanks in advance
Torge
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org