Skip to content

Preserve OHTTP/HPKE error granularity in FFI bindings #1273

Closed as not planned
Closed as not planned
Preserve OHTTP/HPKE error granularity in FFI bindings#1273
Labels
enhancementNew feature or requestffi

Description

@chavic
chavic
opened on Jan 19, 2026

OHTTP/HPKE errors are flattened into generic errors. Clients can’t distinguish “invalid key length” from network/encapsulation failures.

Todo:

  • Export granular error enums for OHTTP/HPKE into FFI.
  • Preserve parse/decode vs transport vs crypto errors.
  • Add negative tests in each binding to assert variant specificity.
  • Keep backwards compatibility by preserving generic error as a top‑level wrapper.

Activity

  1. chavic
    added
    enhancementNew feature or request
    ffi
    on Jan 19, 2026
  2. chavic
    changed the title [-]OHTTP/HPKE error granularity: flattening hides whether the failure is a key format issue, crypto failure, or transport issue; that blocks debugging and correct recovery strategies.,[/-] [+]Preserve OHTTP/HPKE error granularity in FFI bindings[/+] on Jan 19, 2026

  3. spacebear21 commented on Apr 15, 2026

    @spacebear21
    spacebear21
    on Apr 15, 2026
    Collaborator

    Closing as wontfix per my comment here #1431 (review)

  4. spacebear21
    closed this as not plannedon Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestffi

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions