From 483c751b71b767b4b15e62b5accf84210716ab49 Mon Sep 17 00:00:00 2001
From: Luca Toscano you announce that you want all traffic via http: URLs to be redirected
- to the https: ones, for now. If you want client to no longer use the
+ to the https: ones, for now. This is safe and you can remove this again at
+ any time.
+
+ The following has consequences: if you want client to no longer use the
http: URLs, configure:
You can achieve the same with mod_alias and some Redirect configuration,
+ This does two things:
+ You can achieve the same with mod_alias and some Redirect configuration,
basically. If you do it yourself, please make sure to exclude the paths
/.well-known/* from your redirection, otherwise mod_md might have trouble
signing on new certificates.
@@ -524,20 +544,9 @@ MDRenewWindow 10%
it for a specific domain only, use:
When you configure MDRequireHttps permanent, an additional security
- feature is automatically applied: HSTS. This adds the header
- Strict-Transport-Security to responses sent out via https:.
- Basically, this instructs the browser to only perform secure
- communications with that domain. This instruction holds for the
- amount of time specified in the header as 'max-age'.
- This is about half a year as generated by mod_md.
-
- It is therefore advisable to first test the MDRequireHttps temporary
- configuration and switch to permanent only once that works satisfactory.
- Example
MDRequireHttps temporary
Example
MDRequireHttps permanent
+ Permanent (for at least half a year!)
MDRequireHttps permanent
+
+ http:
resources are redirected to the
+ same url with the https:
scheme using the 301
+ status code. This tells clients that this is intended to be forever and
+ the should update any links they have accordingly.
+ https:
requests will carry the header
+ Strict-Transport-Security
with a life time of half a year.
+ This tells the browser that it never (for half a year) shall use http:
+ when talking to this domain name. Browsers will, after having seen this, refuse
+ to contact your unencrypted site. This prevents malicious middleware to
+ downgrade connections and listen/manipulate the traffic. Which is good. But
+ you cannot simply take it back again.
+ Example
<ManagedDomain xxx.yyy>
- MDRequireHttps permanent
+ MDRequireHttps temporary
</ManagedDomain>
x509 specifies a component of an X.509 DN; one of
-C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email
. In Apache 2.1 and
+C,ST,L,O,OU,CN,T,I,G,S,D,UID,Email
. In httpd 2.2.0 and
later, x509 may also include a numeric _n
suffix. If the DN in question contains multiple attributes of the
same name, this suffix is used as a zero-based index to select a
@@ -217,6 +217,12 @@ the SSLOptions
directiv
first (or only) attribute of any DN is added only under a non-suffixed
name; i.e. no _0
suffixed entries are added.
In httpd 2.5.0 and later, an optional _RAW suffix may be
+added to x509 in a DN component, to suppress conversion of
+the attribute value to UTF-8. This must be placed after the index
+suffix (if any). For example, SSL_SERVER_S_DN_OU_RAW
or
+SSL_SERVER_S_DN_OU_0_RAW
could be used.
The format of the *_DN variables has changed in Apache HTTPD
2.3.11. See the LegacyDNStringFormat
option for
SSLOptions
for details.