Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Are headers always defined with ABNF? #74

Closed
Assignees
mnot
@mnot

Description

@mnot

https://tools.ietf.org/html/rfc7230#section-3.2.2 says:

A sender MUST NOT generate multiple header fields with the same field name in a message unless either the entire field value for that header field is defined as a comma-separated list [i.e., #(values)] or the header field is a well-known exception (as noted below).

This ties sender behaviour to how the header field is specified; do we require headers to be defined using ABNF?

If so, we should say so explicitly. If not, we should clarify this requirement.

Furthermore, Section 7 ties handling of specific syntax (e.g., empty lines) to the #-rule. If headers can be defined without ABNF, we should clarify whether that behaviour is required, or specified to #-specified headers.

See alsohttpwg/http-extensions#596

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp