Unrequire remap rules for OCSP #10146
Merged
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.
The change to use FetchSM for OCSP requests (#9591) unintentionally made ATS rely on remap rules, and that effectively broke OCSP if a user sets
remap_requiredto 1. To recover the original behavior which does not rely on remap rules, this introduces a new flag for FetchSM,TS_FETCH_FLAGS_SKIP_REMAP, and the flag enables skipping remap on a transaction initiated byFetchSMeven ifremap_requiredis set to 1.Since the flag is part of TS API, this also enables plugins to make HTTP requests for other servers without remap rules (if FetchSM is used).