Skip to content

Update SslServerCertValidator.md #30

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

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

Update SslServerCertValidator.md #30

wants to merge 1 commit into from

Conversation

yadij
Copy link
Contributor

@yadij yadij commented Mar 25, 2025

  • Fix documentation of 0x01 line terminators (reply only).
  • Fix table display.
  • Add missing concurrency channel documentation and fix related example syntax.
  • Fix various grammar, spelling and typos.

* Fix documentation of 0x01 line terminators (reply only).
* Fix table display
* Add missing concurrency channel documentation and fix related example syntax.
* Fix various grammar, spelling and typos
@yadij yadij requested a review from kinkie March 25, 2025 12:31
@rousskov rousskov self-requested a review March 25, 2025 13:11
*line* refers to a logical input. **body** may contain \\n characters so
each line in this format is delimited by a 0x01 byte instead of the
standard \\n byte.
*`line`* refers to a logical input. **`kv-pairs`** may contain `\n` characters so
Copy link
Contributor

Choose a reason for hiding this comment

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

Please be consistent in formatting "kv-pairs" and similar references, at least in new/modified text. Currently, PR uses a mixture of different formatting approaches, including bold, code, bold code, and plain formatting. I recommend using code formatting for BNF parts like kv-pairs.

standard \\n byte.
*`line`* refers to a logical input. **`kv-pairs`** may contain `\n` characters so
each request message is composed by appending `\n`-terminated lines (including
those `\n` characters) until **`size`** bytes have been received.
Copy link
Contributor

Choose a reason for hiding this comment

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

Please rephrase to avoid "composed until received" phrasing. I recommend dropping the entire "so ..." part and describing kv-pairs and other formatting details (if needed) instead (in a paragraph/blob separate from this "warning" and using BNF where practical).

Similar concerns apply to the response description further below.

@@ -62,29 +62,39 @@ This interface is similar to the SSL certificate generation interface.

Input *line* received from Squid:
Copy link
Contributor

Choose a reason for hiding this comment

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

Avoid the term "line" (that we have to warn about):

Suggested change
Input *line* received from Squid:
Request sent by Squid:
Suggested change
Input *line* received from Squid:
Squid sends requests that use the following format:

... and replace "request" with "command" or similar in the BNF and BNF definitions below.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants