File

mod_strict_https/README.markdown @ 5366:db4c66a1d24b

mod_http_oauth2: Fill in some client metadata defaults Explicit > Implicit Maybe we should actually use these for something as well? :) It's is somewhat an open question of how strictly we should enforce things in the client metadata given that it is somewhat extensible. Especially some of these enum fields which have corresponding IANA registries.
author Kim Alvefur <zash@zash.se>
date Tue, 25 Apr 2023 18:09:08 +0200
parent 1803:4d73a1a6ba68
child 5414:0c8e6269ea38
line wrap: on
line source

---
labels:
summary: HTTP Strict Transport Security
...

Introduction
============

This module implements [HTTP Strict Transport
Security](https://tools.ietf.org/html/rfc6797) and responds to all
non-HTTPS requests with a `301 Moved Permanently` redirect to the HTTPS
equivalent of the path.

Configuration
=============

Add the module to the `modules_enabled` list and optionally configure
the specific header sent.

    modules_enabled = {
      ...
          "strict_https";
    }
    hsts_header = "max-age=31556952"

Compatibility
=============

  ------- --------------
  trunk   Works
  0.9     Works
  0.8     Doesn't work
  ------- --------------