Construct this set of headers, using a HttpStack based upon a ':' delimiter
Clone a source set of HttpHeaders
Clone this set of HttpHeadersView
Create a filter for iterating of a set of named headers. We have to create a filter since we can't pass additional arguments directly to an opApply() method.
Return the value of the provided header, or null if the header does not exist
Return the date value of the provided header, or Time.epoch if the header does not exist
Return the integer value of the provided header, or -1 if the header does not exist
Iterate over the set of headers. This is a shell around the superclass, where we can convert the HttpToken into a HeaderElement instead.
Read all header lines. Everything is mapped rather than being allocated & copied
Control whether headers are duplicated or not. Default behaviour is aliasing instead of copying, avoiding any allocatation overhead. However, the default won't preserve those headers once additional content has been read.
Read all tokens. Everything is mapped rather than being allocated & copied
Parse an input string.
Reset this set of tokens.
Have tokens been parsed yet?
Indicate whether tokens have been parsed or not.
Return the value of the provided header, or null if the header does not exist
Return the integer value of the provided header, or the provided default-vaule if the header does not exist
Return the date value of the provided header, or the provided default-value if the header does not exist
Iterate over the set of tokens
Output the token list to the provided consumer
overridable method to handle the case where a token does not have a separator. Apparently, this can happen in HTTP usage
Create a filter for iterating over the tokens matching a particular name.
Implements a filter for iterating over tokens matching a particular name. We do it like this because there's no means of passing additional information to an opApply() method.
Return a char[] representing the output. An empty array is returned if output was not configured. This perhaps could just return our 'output' buffer content, but that would not reflect deletes, or seperators. Better to do it like this instead, for a small cost.
Add a token with the given name. The content is provided via the specified delegate. We stuff this name & content into the output buffer, and map a new Token onto the appropriate buffer slice.
Add a simple name/value pair to the output
Add a name/integer pair to the output
Add a name/date(long) pair to the output
remove a token from our list. Returns false if the named token is not found.
Maintains a set of input headers. These are placed into an input buffer and indexed via a HttpStack.