Document checkLink headers field and retry behavior#19
Closed
promptless[bot] wants to merge 3 commits into
Closed
Conversation
Add documentation for new checkLink capabilities from PR #253: - New `headers` field for custom HTTP headers (WAF allowlist support) - Automatic retry with exponential backoff on 429/5xx - HEAD fallback on final 429/403 - Updated default statusCodes to accurate value
Updated behavior description to specify: - Exact retry count: up to 3 retries (4 total attempts) - Specific backoff timing: 1s → 2s → 4s - Retry-After header support (capped at 10 seconds)
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
1 participant
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.
Open this suggestion in Promptless to view citations and reasoning process
Updates the doc-detective-doc-testing skill to document new checkLink capabilities: the
headersfield for WAF/bot-protection bypass, automatic retry with exponential backoff on 429/5xx responses, HEAD fallback, and corrected default status codes.Tip: Planning a big docs refactor? Use Deep Analysis to get help with the heavy lifting 🔍