Reconsider: Request / Response Execution Context Header Requirement #108
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
…atch Clarified requirements for header values in requests and responses for execution context. The original intent was that there may be scenarios where the response value provides a different alias, or redirected version that is available. This was worded carefully in the statement before and after in the original content. Adding this line in the last update overrides that intent. Signed-off-by: Travis Gosselin <[email protected]>
omnipitous
reviewed
Oct 28, 2025
acchristensen
approved these changes
Oct 28, 2025
acchristensen
left a comment
acchristensen
left a comment
There was a problem hiding this comment.
looks good to me. just as a heads up, I think we might come back to this to help provide some clarity around the statement. It's a bit long. But I'm honestly not sure how I would do that, right now, that wouldn't be more confusing.
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.
Clarified requirements for header values in requests and responses for execution context. The original intent was that there may be scenarios where the response value provides a different alias, or redirected version that is available. This was worded carefully in the statement before and after in the original content. Adding this line in the last update overrides that intent.