Skip to content

HTTP/2: Valid response trailers are rejected. #236

Open

Description

@Ph4ntomas

From the RFC: 8.1.2.1. Pseudo-Header Fields

Pseudo-header fields MUST NOT appear in trailers.

This is properly handled for request headers, by checking the nth_header parameter in validate_header, however the response validation does not contain such check, and tries to enforce that responses trailers contain :status pseudo-header

Activity

  1. Ph4ntomas commented on Jul 24, 2025

    @Ph4ntomas
    Author

    I went ahead and opened #237 to fix the issue

  2. daurnimator commented on Jul 29, 2025

    @daurnimator
    Owner

    @Ph4ntomas there can be many request headers; e.g. if there is a 100 (Continue). ==> just because it's not the first header block doesn't mean it's a trailer.

  3. Ph4ntomas commented on Jul 29, 2025

    @Ph4ntomas
    Author

    there can be many request headers; e.g. if there is a 100 (Continue). ==> just because it's not the first header block doesn't mean it's a trailer.

    Ah right, I did not take into account interim responses.

    That doesn't change the issue however. Valid trailers are being rejected because :status is expected on them.

    Do you have an idea on how to ensure we're indeed handling a trailer ?

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions