Skip to content

terminology/definition of where request target and response status live #372

Description

@reschke

Section 2.1 has:

A client sends an HTTP request to a server in the form of a request message, beginning with a method (Section 7) and URI, followed by header fields containing request modifiers, client information, and representation metadata (Section 4), and finally a payload body (if any, Section 6.3.3).

A server responds to a client's request by sending one or more HTTP response messages, each beginning with a success or error code (Section 9), possibly followed by header fields containing server information, resource metadata, and representation metadata (Section 4), and finally a payload body (if any, Section 6.3.3).

So this is also specific to 1.1.

My proposal would be to define terms for request-line and status-line that are indenpendant of the protocol version.

For 1.1, these would map to what we had before (and might have to include the "Host" header field, right?).

For 2 (and 3, I guess), they would map to the pseudo header fields (all?).

We'd also have to fix the text above, as some ("Host") or all (pseudo header fields) are actually contained in the header field section.

Activity

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

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions