Skip to content

Reconsider: Request / Response Execution Context Header Requirement #108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 29, 2025
Merged

Reconsider: Request / Response Execution Context Header Requirement #108

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7ce1a05
Reconsider: Request / Response Execution Context Header Required to M…
travisgosselin Oct 28, 2025
caeec69
fix: clarify propagation and response requirements for context header
travisgosselin Oct 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions standards/request-response.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -509,9 +509,7 @@ Sps-Cors-Error: bad origin
- It **MUST** only contain ASCII lowercase letters (a–z), digits (0–9), underscore (`_`), or hyphen (`-`).
- It **MUST NOT** contain accented/diacritic or non-ASCII characters.
- The header value **SHOULD** contain human-readable tag for the context.
- The original request header value **SHOULD** be propagated to any outgoing requests to retain the context for downstream usage.
- The header **MUST** be supplied in the response for every request containing the header, and match the original requested value.
- The header **SHOULD** be supplied in the response for every request in general, if applicable to the API, even if just defaulting to __prod__.
- The header **SHOULD** be propagated to outgoing requests for downstream context retention and **MUST** be supplied in responses when provided in the request, reflecting either the requested value or the properly transformed value utilized for execution.

```note
The allowed character set is intentionally conservative and may expand in the future. Implementations should avoid hard-coding assumptions and be prepared for a broader set if the standard is updated.
Expand Down
Loading