英語 での Header fields の使用例とその 日本語 への翻訳
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
-
Programming
Misc. TCP header fields.
Client request might include. The number of request header fields.
Layer-2 header fields When available.
The formal definition of these header fields is as follows:.
Unknown header fields are ignored, as per[RFC2616].
Is always terminated by the first empty line after the header fields.
These header fields occur in at least two contexts:.
In particular, they frequently add, remove, or reorder header fields.
Extension header fields no longer specifically called out.
This document defines the HTTP Cookie and Set-Cookie header fields.
The IPv4 base header fields are classified as follows:.
All the core concepts, such as HTTP methods, status codes,URIs, and header fields, remain in place.
(4) Two additional header fields that can be used to.
All the core concepts, such as HTTP methods, status codes,URIs, and header fields, remain in place.
Two optional header fields that can be used to further.
An ideal solution segregates access to the dynamictable based on the entity that is constructing header fields.
Add the list of header fields named to the ignored list.
All basic HTTP/1.1 concepts such as HTTP methods, status codes,URI, and header fields are the same.
Furthermore, HTTP header fields are often repetitive and verbose.
All the core concepts found in HTTP 1.1, such as HTTP methods, status codes,URIs, and header fields, remain in place.
These header fields apply only to the message being transmitted.
Limits the number of HTTP request header fields that will be accepted from the client.
All of the header fields defined in this document are subject to the general syntactic rules for header fields specified in RFC 822.
The Trailer header field can be used to indicate which header fields are included in a trailer(see section 14.40).
To use different header fields in conditions, choose Edit Header List from the first pop-up menu.
Utilities for header fields A few utility procedures to parse and generate MIME-specific header fields. .
Will remove all header fields with the given name from the message. This is useful mainly for removing bogus Reply-To: headers. .
The HTTP 431 Request Header Fields Too Large response status code indicates that the server is unwilling to process the request because its header fields are too large.
The HTTP 431 Request Header Fields Too Large response status code indicates that the server refuses to process the request because the request's HTTP headers are too long.