Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make OPTIONAL violation report keys clearer #856

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Make OPTIONAL violation report keys clearer #856

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions draft-ietf-httpbis-expect-ct.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -470,9 +470,9 @@ request that failed the CT compliance check. The value is provided as a string.
* "port": the value is the port to which the UA made the original request that
failed the CT compliance check. The value is provided as an integer.

* "scheme": the value is the scheme with which the UA made the original request
that failed the CT compliance check. The value is provided as a string. This
key is optional and is assumed to be "https" if not present.
* "scheme": (OPTIONAL) the value is the scheme with which the UA made the
original request that failed the CT compliance check. The value is provided as a
string and assumed to be "https" if not present.

* "effective-expiration-date": the value indicates the Effective Expiration Date
(see {{storage-model}}) for the Expect-CT Host that failed the CT compliance
Expand Down Expand Up @@ -530,7 +530,7 @@ by an Expect-CT policy in enforce or report-only mode. The value is provided
as a string. The UA MUST set this value to "enforce" if the Expect-CT metadata
indicates an `enforce` configuration, and "report-only" otherwise.

* "test-report": the value is set to true if the report is being sent by a
* "test-report": (OPTIONAL) the value is set to true if the report is being sent by a
testing client to verify that the report server behaves correctly. The
value is provided as a boolean, and MUST be set to true if the report serves
to test the server's behavior and can be discarded.
Expand Down