Array of accepted encoding for content compression from the HTTP header
Array of accepted encoding for content compression from the HTTP header
For example, give then header Accept-Encoding: gzip, deflate
, then an array containing
gzip
and defalte
will be returned.
Body of the HTTP request
Body of the HTTP request
Returns the length of the content from the Content-Length
header.
Returns the length of the content from the Content-Length
header. If not set, 0
is returned.
Content type of the body expressed as a MIME type.
Content type of the body expressed as a MIME type. e.g. text/plain
.
HTTP End point for this request
HTTP End point for this request
HTTP request headers
HTTP request headers
HTTP version
HTTP version
Returns the If-Modified-Since header as Some(Date).
Returns the If-Modified-Since header as Some(Date). None is returned if the header not present or cannot be parsed
True
if and only if 100 continue is expected to be returned
True
if and only if 100 continue is expected to be returned
True
if and only if the contents of this HTTP request will be arriving in subsequent HTTPChunks
True
if and only if the contents of this HTTP request will be arriving in subsequent HTTPChunks
Note that if True
, this HTTP request will NOT have any content. The content will be coming
in subsequent HTTP chunks and sent for processing as HttpChunkEvent
.
True
if and only if is connection is to be kept alive and the channel should NOT be closed
after a response is returned.
True
if and only if is connection is to be kept alive and the channel should NOT be closed
after a response is returned.
This flag is controlled by the existence of the keep alive HTTP header.
Connection: keep-alive
True
if and only if this is a request to upgrade to a websocket connection
True
if and only if this is a request to upgrade to a websocket connection
Note: Firefox sends "Connection: keep-alive, Upgrade" rather than "Connection: Upgrade"
Netty HTTP request message
Our supported encoding; None
if acceptedEncodings
does not contain an encoding that we support
HTTP request message for the current event (as opposed to an initial HTTP required to triggered a HTTP Chunk or web socket event).
Netty HTTP request message