DotNetty.Codecs.Http
Returns true if the raw value of this {@link Cookie},
was wrapped with double quotes in original Set-Cookie header.
Checks to see if this Cookie can only be accessed via HTTP.
If this returns true, the Cookie cannot be accessed through
client side script - But only if the browser supports it.
For more information, please look "http://www.owasp.org/index.php/HTTPOnly".
Standard HTTP header names.
These are all defined as lowercase to support HTTP/2 requirements while also not
violating HTTP/1.x requirements.New header names should always be lowercase.
Deep copy of the headers.
A deap copy of this.
The OPTIONS method represents a request for information about the communication options
available on the request/response chain identified by the Request-URI. This method allows
the client to determine the options and/or requirements associated with a resource, or the
capabilities of a server, without implying a resource action or initiating a resource
retrieval.
The GET method means retrieve whatever information (in the form of an entity) is identified
by the Request-URI. If the Request-URI refers to a data-producing process, it is the
produced data which shall be returned as the entity in the response and not the source text
of the process, unless that text happens to be the output of the process.
The HEAD method is identical to GET except that the server MUST NOT return a message-body
in the response.
The POST method is used to request that the origin server accept the entity enclosed in the
request as a new subordinate of the resource identified by the Request-URI in the
Request-Line.
The PUT method requests that the enclosed entity be stored under the supplied Request-URI.
The PATCH method requests that a set of changes described in the
request entity be applied to the resource identified by the Request-URI.
The DELETE method requests that the origin server delete the resource identified by the
Request-URI.
The TRACE method is used to invoke a remote, application-layer loop- back of the request
message.
This specification reserves the method name CONNECT for use with a proxy that can dynamically
switch to being a tunnel
The response code and its description of HTTP or its derived protocols, such as
RTSP and
ICAP.
100 Continue
101 Switching Protocols
102 Processing (WebDAV, RFC2518)
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information (since HTTP/1.1)
204 No Content
205 Reset Content
206 Partial Content
207 Multi-Status (WebDAV, RFC2518)
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other (since HTTP/1.1)
304 Not Modified
305 Use Proxy (since HTTP/1.1)
307 Temporary Redirect (since HTTP/1.1)
308 Permanent Redirect (RFC7538)
400 Bad Request
401 Unauthorized
402 Payment Required
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Requested Range Not Satisfiable
417 Expectation Failed
421 Misdirected Request
421 Status Code
422 Unprocessable Entity (WebDAV, RFC4918)
423 Locked (WebDAV, RFC4918)
424 Failed Dependency (WebDAV, RFC4918)
425 Unordered Collection (WebDAV, RFC3648)
426 Upgrade Required (RFC2817)
428 Precondition Required (RFC6585)
429 Too Many Requests (RFC6585)
431 Request Header Fields Too Large (RFC6585)
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
506 Variant Also Negotiates (RFC2295)
507 Insufficient Storage (WebDAV, RFC4918)
510 Not Extended (RFC2774)
511 Network Authentication Required (RFC6585)
A queue that is used for correlating a request and a response.
Keep-alive only works if the client can detect when the message has ended without relying on the connection being
closed.
https://tools.ietf.org/html/rfc7230#section-6.3
https://tools.ietf.org/html/rfc7230#section-3.3.2
https://tools.ietf.org/html/rfc7230#section-3.3.3
The HttpResponse to check
true if the response has a self defined message length.
The source codec that is used in the pipeline initially.
Removes this codec (i.e. all associated handlers) from the pipeline.
A codec that the source can be upgraded to.
Gets all protocol-specific headers required by this protocol for a successful upgrade.
Any supplied header will be required to appear in the {@link HttpHeaderNames#CONNECTION} header as well.
Prepares the {@code upgradeHeaders} for a protocol update based upon the contents of {@code upgradeRequest}.
This method returns a boolean value to proceed or abort the upgrade in progress. If {@code false} is
returned, the upgrade is aborted and the {@code upgradeRequest} will be passed through the inbound pipeline
as if no upgrade was performed. If {@code true} is returned, the upgrade will proceed to the next
step which invokes {@link #upgradeTo}. When returning {@code true}, you can add headers to
the {@code upgradeHeaders} so that they are added to the 101 Switching protocols response.
Performs an HTTP protocol upgrade from the source codec. This method is responsible for
adding all handlers required for the new protocol.
ctx the context for the current handler.
upgradeRequest the request that triggered the upgrade to this protocol.
Creates a new UpgradeCodec for the requested protocol name.
Invoked by {@link HttpServerUpgradeHandler} for all the requested protocol names in the order of
the client preference.The first non-{@code null} {@link UpgradeCodec} returned by this method
will be selected.
Interface to enable creation of IPostHttpData objects
Creates an URL-encoded URI from a path string and key-value parameter pairs.
This encoder is for one time use only. Create a new instance for each URI.
{@link QueryStringEncoder} encoder = new {@link QueryStringEncoder}("/hello");
encoder.addParam("recipient", "world");
assert encoder.toString().equals("/hello?recipient=world");
Returns the closing status code as per http://tools.ietf.org/html/rfc6455#section-7.4 RFC 6455.
If a getStatus code is set, -1 is returned.
Returns the reason text as per http://tools.ietf.org/html/rfc6455#section-7.4 RFC 6455
If a reason text is not supplied, an empty string is returned.
The reserved bit value to ensure that no other extension should interfere.
Marker interface which all WebSocketFrame decoders need to implement. This makes it
easier to access the added encoder later in the
Marker interface which all WebSocketFrame encoders need to implement. This makes it
easier to access the added encoder later in the .
Events that are fired to notify about handshake status
The Handshake was started but the server did not response yet to the request
The Handshake was complete succesful and so the channel was upgraded to websockets
Flag to indicate if this frame is the final fragment in a message. The first fragment (frame)
may also be the final fragment.
RSV1, RSV2, RSV3 used for extensions