Skip to content

Decide and enforce imp_ext reserved-field protection #1143

Description

@aram356

Source finding from PR #1049 documentation refresh: request_ext is guarded as a reserved field but imp_ext is not, despite prior documentation claiming protection for both.

Acceptance: decide whether imp_ext is reserved, align implementation and documentation, and add positive and negative tests that lock the chosen behavior.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingrustPull requests that update rust code

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions