Browsers are rather smart, but also dumb. This uses the `Expires` header
alongside `cache-control` to better prompt the browser to actually
cache.
Unfortunately, firefox still tries to "race" its own cache, in an
attempt to respond to requests faster, so still ends up making a bunch
of requests which could have been cached. Doesn't appear there's any way
around this.
// Per <https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-appid-and-facets-v2.0-id-20180227.html#determining-the-facetid-of-a-calling-application>:
"ids": [
//
// Per <https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-appid-and-facets-v2.0-id-20180227.html#determining-the-facetid-of-a-calling-application>:
// "In the Web case, the FacetID MUST be the Web Origin [RFC6454]
//
// of the web page triggering the FIDO operation, written as
// "In the Web case, the FacetID MUST be the Web Origin [RFC6454]
// a URI with an empty path. Default ports are omitted and any
// of the web page triggering the FIDO operation, written as
// path component is ignored."
// a URI with an empty path. Default ports are omitted and any
//
// path component is ignored."
// This leaves it unclear as to whether the path must be empty,
//
// or whether it can be non-empty and will be ignored. To be on
// This leaves it unclear as to whether the path must be empty,
// the safe side, use a proper web origin (with empty path).
// or whether it can be non-empty and will be ignored. To be on
&CONFIG.domain_origin(),
// the safe side, use a proper web origin (with empty path).