Опубликованный пакет / CLIR
ietf.http_semantics
v0.1.0HTTP Semantics
Пломба §208
sha256:fd6048db78d80361b1e8c0a161bf880ff6857726fc876de926f05f2c862e668dПодключить /
law.toml[dependencies] ietf.http_semantics = "0.1.0"
Получить канонические байты
curl -O /blobs/fd6048db78d80361b1e8c0a161bf880ff6857726fc876de926f05f2c862e668d.lawir.json
Все адресуемые узлы пакета. Помеченные internal — не часть контракта: сослаться на них из другого пакета нельзя (§24). Свою страницу имеют только публичные символы.
symbol_decl — 43
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| ALLOW_IN_405 | the origin server MUST generate an Allow header field in a 405 response (Section 15.5.6) | internal | |
| AllowField | the Allow header field | internal | |
| HOST_FIRST_FIELD | a user agent that sends Host SHOULD send it as the first field in the header section (Section 7.2) | internal | |
| HOST_IN_REQUEST | a user agent MUST generate a Host header field in a request unless it sends that information as an :authority pseudo-header field (Section 7.2) | internal | |
| HostField | the Host header field | internal | |
| NO_APPLY_BEFORE_HEADER_SECTION | a server MUST NOT apply a request to the target resource until it receives the entire request header section (Section 5.3) | internal | |
| NO_CONTENT_IN_204 | a 204 response is terminated by the end of the header section; it cannot contain content or trailers (Section 15.3.5) — no BCP 14 key word | internal | |
| NO_DUPLICATE_FIELD_LINES | a sender MUST NOT generate multiple field lines with the same name in a message (Section 5.3) | internal | |
| NO_REORDER_BY_PROXY | a proxy MUST NOT change the order of field line values when forwarding a message (Section 5.3) | internal | |
| OriginServer | the origin server | internal | |
| PRESENT_REPRESENTATION | the user agent SHOULD present the enclosed representation to the user (Section 15.5.2) | internal | |
| Proxy | a proxy | internal | |
| REPEAT_WITH_AUTHORIZATION | the user agent MAY repeat the request with a new or replaced Authorization header field (Section 15.5.2) | internal | |
| RFC9110_DOCUMENT | RFC 9110, HTTP Semantics | internal | |
| Sender | a sender | internal | |
| Server | a server | internal | |
| UserAgent | the user agent | internal | |
| WWW_AUTHENTICATE_IN_401 | the server generating a 401 response MUST send a WWW-Authenticate header field (Section 15.5.2) | internal | |
| WwwAuthenticateField | the WWW-Authenticate header field | internal | |
| acts_as | the participant acts in this role for the exchange | 1 | internal |
| already_attempted_authentication | the user agent has already attempted authentication at least once | internal | |
| applied_before_header_section_complete | the server applied the request to the target resource before receiving the entire request header section | internal | |
| carries_content | the message carries content | internal | |
| carries_trailers | the message carries a trailer section | internal | |
| duplicate_field_lines | the message carries multiple field lines with this field name | internal | |
| field_allows_comma_list | the field's definition allows multiple field line values to be recombined as a comma-separated list | internal | |
| field_forbids_comma_list | the field's definition does not allow its values to be recombined as a comma-separated list | internal | |
| generated_by | the message was generated by this participant | internal | |
| has_field | the message carries this field | internal | |
| host_not_sent_first | the Host field is present but is not the first field in the header section | internal | |
| host_sent_first | the Host field is the first field in the header section of the request | internal | |
| ill_formed_message | the message is not a well-formed message of the protocol | internal | |
| is_request | the message is a request | internal | |
| lacks_field | the message does not carry this field | internal | |
| omits_authority_pseudo_header | the request does not carry an :authority pseudo-header field | internal | |
| presented_representation_to_user | the user agent presented the enclosed representation to the user | internal | |
| preserved_field_values_order | the proxy preserved the order of field line values when forwarding the message | internal | |
| reordered_field_values | the proxy changed the order of field line values when forwarding the message | internal | |
| repeated_with_authorization | the user agent repeated the request with a new or replaced Authorization field | internal | |
| same_challenge_as_prior | the 401 response contains the same challenge as the prior response | internal | |
| sends_authority_pseudo_header | the request carries the host information as an :authority pseudo-header field | internal | |
| status_code | the response status code of the message | internal | |
| withheld_representation_from_user | the user agent did not present the enclosed representation to the user | internal |
type_decl — 3
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| FieldName | a header or trailer field name | internal | |
| HttpMessage | an HTTP message (request or response) | internal | |
| HttpRole | the role in which a participant is addressed by a requirement | internal |
rule — 19
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| ApplyingBeforeHeaderSectionDeviates | applying a request before the entire header section is received deviates from the prohibition of Section 5.3 | 1 | internal |
| ContentIn204IsIllFormed | a 204 response is terminated by the end of the header section; it cannot contain content | 1 | internal |
| DuplicateFieldLinesDeviate | generating multiple field lines with the same name deviates from the prohibition of Section 5.3, unless the field allows a comma-separated list | 1 | internal |
| DuplicateLinesOfAListFieldConform | multiple field lines of a field whose definition allows a comma-separated list are within the exception of Section 5.3 | 1 | internal |
| HostNotSentFirstDeviates | sending Host other than as the first field deviates from the recommendation of Section 7.2 | 1 | internal |
| HostSentFirstConforms | sending Host as the first field conforms to the recommendation of Section 7.2 | 1 | internal |
| PresentingRepresentationConforms | presenting the enclosed representation conforms to the recommendation of Section 15.5.2 | 1 | internal |
| PreservingOrderConforms | preserving the order of field line values when forwarding conforms to Section 5.3 | 1 | internal |
| ReorderingByProxyDeviates | changing the order of field line values when forwarding deviates from the prohibition of Section 5.3 | 1 | internal |
| RepeatingRequestExercisesTheOption | repeating the request with an Authorization field is the exercise of a truly optional item | 1 | internal |
| RequestWithAuthorityPseudoHeaderConforms | a request that sends the host information as an :authority pseudo-header field is within the exception of Section 7.2 | 1 | internal |
| RequestWithHostConforms | a request that carries a Host field conforms to the requirement of Section 7.2 | 1 | internal |
| RequestWithoutHostDeviates | a request with neither a Host field nor an :authority pseudo-header field deviates from the requirement of Section 7.2 | 1 | internal |
| Status401WithChallengeConforms | a 401 response that carries a WWW-Authenticate field conforms to the requirement of Section 15.5.2 | 1 | internal |
| Status401WithoutChallengeDeviates | a 401 response without a WWW-Authenticate field deviates from the requirement of Section 15.5.2 | 1 | internal |
| Status405WithAllowConforms | a 405 response that carries an Allow field conforms to the requirement of Section 15.5.6 | 1 | internal |
| Status405WithoutAllowDeviates | a 405 response without an Allow field deviates from the requirement of Section 15.5.6 | 1 | internal |
| TrailersIn204AreIllFormed | a 204 response is terminated by the end of the header section; it cannot contain trailers | 1 | internal |
| WithholdingRepresentationDeviates | withholding the enclosed representation deviates from the recommendation of Section 15.5.2 | 1 | internal |
assertion — 20
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| assert-1 | — | 1 | internal |
| assert-10 | — | 1 | internal |
| assert-11 | — | 1 | internal |
| assert-12 | — | 1 | internal |
| assert-13 | — | 1 | internal |
| assert-14 | — | 1 | internal |
| assert-15 | — | 1 | internal |
| assert-16 | — | 1 | internal |
| assert-17 | — | 1 | internal |
| assert-18 | — | 1 | internal |
| assert-19 | — | 1 | internal |
| assert-2 | — | 1 | internal |
| assert-20 | — | 1 | internal |
| assert-3 | — | 1 | internal |
| assert-4 | — | 1 | internal |
| assert-5 | — | 1 | internal |
| assert-6 | — | 1 | internal |
| assert-7 | — | 1 | internal |
| assert-8 | — | 1 | internal |
| assert-9 | — | 1 | internal |
fragment — 6
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC9110_S15_3_5 | — | internal | |
| RFC9110_S15_5_2 | — | internal | |
| RFC9110_S15_5_6 | — | internal | |
| RFC9110_S2_2 | — | internal | |
| RFC9110_S5_3 | — | internal | |
| RFC9110_S7_2 | — | internal |
publication — 1
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC9110_EN_TEXT | — | internal |
source_edition — 1
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC9110_EN | RFC 9110 (R. Fielding, M. Nottingham, J. Reschke, eds.) | internal |
source_work — 1
| Узел | Подпись | Анкеры §194 | |
|---|---|---|---|
| RFC9110 | HTTP Semantics | internal |