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.

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

client-cert: AD review feedback #2406

Merged
merged 4 commits into from Feb 21, 2023
Merged

client-cert: AD review feedback #2406

merged 4 commits into from Feb 21, 2023

Conversation

b---c
Copy link
Contributor

@b---c b---c commented Feb 15, 2023

AD review feedback (thread at https://lists.w3.org/Archives/Public/ietf-http-wg/2023JanMar/0088.html) and some minor editorial updates

Copy link
Contributor

@MikeBishop MikeBishop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good; two nits.

@@ -323,14 +323,14 @@ from the TTRP). A TTRP MUST sanitize the incoming request before forwarding it
on by removing or overwriting any existing instances of the fields. Otherwise,
arbitrary clients can control the field values as seen and used by the backend
server. It is important to note that neglecting to prevent field injection does
not "fail safe" in that the nominal functionality will still work as expected
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect this was correct before; "fail safe" is a verb, where "fail-safe" would be an adjective or used as a noun.

draft-ietf-httpbis-client-cert-field.md Outdated Show resolved Hide resolved
Co-authored-by: Mike Bishop <mbishop@evequefou.be>
@b---c
Copy link
Contributor Author

b---c commented Feb 21, 2023

thanks Mike, nits have been addressed

@b---c b---c merged commit 0c27961 into main Feb 21, 2023
@b---c b---c deleted the cert/ad-review branch February 21, 2023 20:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

3 participants