Filter state: Add missing api to get filterstate format working #35559
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.
Commit Message: Filter state: Add missing api to get filterstate format working
Additional Description:
Consider the case where filter state is being set using the
set_filter_state
filter:Now if one try to use the value from the filter state, for example in the tunneling config hostname:
Then filter state formatter fails to find the value because here, it invokes
serializeAsString()
on the stored filter state object, which isUpstreamServerName
instance in this case and it is missing this function.I think similar change would be required for other well-known name objects as well like Upstream subject alt names and alpn application protocols.
related #30674