Documentation update for issue #67 #129
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt to resolve issue 67
The user wants to update the documentation to include information about certificate revocation checking methods such as CRLs and OCSP. Among the potential documents, the most relevant is the "content/nginx/fips-compliance-nginx-plus.md" document, which discusses FIPS compliance and cryptographic modules, but does not currently mention revocation checking methods. The "content/unit/certificates.md" document covers TLS certificates and their management but does not detail revocation checking methods. The "content/includes/nginx-one/add-file/existing-ssl-bundle.md" and "content/includes/nginx-one/add-file/new-ssl-bundle.md" are about uploading SSL certificates and keys, not about revocation methods. The "content/controller/services/manage-certs.md" discusses managing certificates via API but not about revocation checking. The "content/includes/nap-waf/config/common/signature-sets-in-default-policy.md" and "content/includes/nap-waf/config/common/signature-sets-in-default-policy.md" are about attack signatures, unrelated to certificate revocation. The "content/includes/nap-waf/config/common/time-based-sig-overview.md" is about signature timing, not revocation. The "content/includes/nap-waf/config/common/basic-signature-sets-included-in-app-protect.md" and "content/includes/nap-waf/config/common/grpc-content-profiles.md" are unrelated. The "content/controller/services/manage-gateways.md" and "content/controller/services/manage-apps.md" are about managing services and apps, not certificates. The "content/installation/helm/acm/dev-portal-helm-configurations/configure-devportal-helm-api-mtls.md" and "content/controller/platform/integrations/otlp-integration.md" are unrelated.
Since none of the existing documents directly mention revocation checking methods, the best approach is to update the most relevant document that discusses SSL/TLS certificates, which is "content/unit/certificates.md". This document can be expanded to include a section on revocation checking methods such as CRLs and OCSP, providing users with comprehensive guidance on certificate validation.