#52: Clarification of section 2.3.1
Changes (by y...@checkpoint.com):
* status: assigned = closed
* resolution: = fixed
Comment:
Solved in -04
--
-+
Reporter: Tom Ritter | Owner: pal...@google.com
Type: defect
#52: Clarification of section 2.3.1
Changes (by palmer@…):
* owner: draft-ietf-websec-key-pinning@… = palmer@…
* status: new = assigned
--
-+---
Reporter: Tom Ritter | Owner: palmer@…
Type: defect | Status: assigned
#52: Clarification of section 2.3.1
I'd suggest the following change to 2.3.1, clarifying it's
required-ness and a max-age of 0.
2.3.1. max-age
max-age specifies the number of seconds, after the reception of the
Public-Key-Pins HTTP Response Header, during which the UA regards the