TODO maybe it would be better if all the constant headers are enum and not independet strings ekrigro public static enum Type { ACCEPT("Accept"); private final String value; Type(String value) { this.value = value; } public String getValue() { return value; } }
Element that contains some user defined meta information about the document. Example:
Header header = new Header("inspired by", "William Shakespeare"); A header is immutable, but unlike body it can be read multiple times. The {@link Header} abstraction hides how the headerdata is represented in memory; instead, it commits to the ability to write itself to XML infoset.
When a message is received from the transport and being processed, the processor needs to "peek" some information of a header, such as the tag name, the mustUnderstand attribute, and so on. Therefore, the {@link Header} interface exposes those informationas properties, so that they can be checked without replaying the infoset, which is efficiently but still costly.
A {@link Header} may belong to more than one {@link HeaderList}due to wrapping of {@link Message}. @see HeaderList @see Headers
A header is immutable, but unlike body it can be read multiple times. The {@link Header} abstraction hides how the headerdata is represented in memory; instead, it commits to the ability to write itself to XML infoset.
When a message is received from the transport and being processed, the processor needs to "peek" some information of a header, such as the tag name, the mustUnderstand attribute, and so on. Therefore, the {@link Header} interface exposes those informationas properties, so that they can be checked without replaying the infoset, which is efficiently but still costly.
A {@link Header} may belong to more than one {@link HeaderList}due to wrapping of {@link Message}. @see HeaderList @see Headers
Header Handling:
Any SIP header whose grammar is of the form:
The relative order of header objects within messages is not significant. However, it is RECOMMENDED that required header and headers which are needed for proxy processing (Via, Route, Record-Route, Proxy-Require, Max-Forwards, and Proxy-Authorization, for example) appear towards the top of the message to facilitate rapid parsing.
The relative order of header objects with the same field name is important. Multiple headers with the same name MAY be present in a message if and only if the entire field-value for that header field can be defined as a comma-separated list as defined by RFC 3261. The exceptions to this rule are the WWW-Authenticate, Authorization, Proxy-Authenticate, and Proxy-Authorization header fields. Multiple header objects with these names MAY be present in a message, but since their grammar does not follow the general form listed above, they MUST NOT be combined into a single header field row when sent over the network.
Even though an arbitrary number of parameter pairs may be attached to a header object, any given parameter-name MUST NOT appear more than once. @author BEA Systems, NIST @version 1.2
An HTTP header.
@author Remy Maucherat @author Mike Bowler @author Oleg Kalnichevski @version $Revision: 1.17 $ $Date: 2004-09-15 16:44:02 -0400 (Wed, 15 Sep 2004) $The HTTP header fields follow the same generic format as that given in Section 3.1 of RFC 822. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The field value MAY be preceded by any amount of LWS, though a single SP is preferred.
message-header = field-name ":" [ field-value ] field-name = token field-value = *( field-content | LWS ) field-content = <the OCTETs making up the field-value and consisting of either *TEXT or combinations of token, separators, and quoted-string>@author Remy Maucherat @author Oleg Kalnichevski @version $Revision: 569636 $
Header...
Header object represents the contents and semantics of a <SOAP-ENV:Header> element.
@author Matthew J. Duftler (duftler@us.ibm.com)
@author Sanjiva Weerawarana (sanjiva@watson.ibm.com)
Super interface of all headers contained within a packet. Each packet contans 0 or more protocol specific headers that are typically daisy chained. The header are part of the packet data as returned by live packet capture or as read from a capture/trace file.
This header interface does not provide any mutable methods outside of returning a mutable ByteBuffer with the header's content. The reason for this is that the header structure is built based upon the contents of the buffer and the header's NPL definition. If the header's contents have been modified structurally the entire has to be redecoded again.
The interface does not provide any methods with dealing with fields within this header or sub headers if they exist. You use the type specific header interface to check for existance of fields and sub headers and then access those fields and sub headers.
@author Mark Bednarczyk @author Sly Technologies, Inc.Normally, you don't need to manipulate the Header object directly - JRobin framework does it for you.
@author Sasa Markovic
Header object that is used to represent a basic form for the HTTP request message. This is used to extract values such as the request line and header values from the request message. Access to header values is done case insensitively. As well as providing the header values and request line values this will also provide convenience methods which enable the user to determine the length of the body this message header prefixes. @author Niall Gallagher
The following features are implemented:
Copyright (c) 2006 Dominik Schulz Copyright (c) 2006 Florian Lindner Copyright (c) 2006 Philip Hartmann This file is part of jHTTPd. jHTTPd is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. jHTTPd is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with jHTTPd; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA@author Dominik
| |
| |
| |