Skip to content

Expect: 100-continue not implemented for HTTP/2 #2743

Open
@rawler

Description

@rawler

Hyper (server) does not support sending 100 Continue upon receiving an HTTP/2 request with a Expect: 100-continue specified. This is currently blocking moving a project from HTTP/1.1 to HTTP2 for me.

I've been digging through the specs, and as far as I can tell;

HTTP's existing semantics remain unchanged.

An origin server MUST, upon receiving an HTTP/1.1 (or later)
request-line and a complete header section that contains a
100-continue expectation and indicates a request message body will
follow, either send an immediate response with a final status code,
if that status can be determined by examining just the request-line
and header fields, or send an immediate 100 (Continue) response to
encourage the client to send the request's message body. The origin
server MUST NOT wait for the message body before sending the 100
(Continue) response.

I think the simple solution here is to try to replicate the behavior hyper already expose for HTTP/1.1? #838

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-http2Area: HTTP/2 specific.A-serverArea: server.C-bugCategory: bug. Something is wrong. This is bad!E-mediumEffort: medium. Some knowledge of how hyper internal works would be useful.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions