Instances of this class will only be created transiently during header parsing and will never appear in HttpMessage.header.
Instances of this class will only be created transiently during header parsing and will never appear in HttpMessage.header. To access the Content-Length, see subclasses of HttpEntity.
Instances of this class will only be created transiently during header parsing and will never appear in HttpMessage.header.
Instances of this class will only be created transiently during header parsing and will never appear in HttpMessage.header. To access the Content-Type, see subclasses of HttpEntity.
Superclass for user-defined custom headers defined by implementing name
and value
.
Superclass for user-defined custom headers defined by implementing name
and value
.
Prefer to extend ModeledCustomHeader and ModeledCustomHeaderCompanion instead if planning to use the defined header in match clauses (e.g. in the routing layer of Akka HTTP), as they allow the custom header to be matched from RawHeader and vice-versa.
for a full definition of the http cookie header fields, see http://tools.ietf.org/html/rfc6265
for a full definition of the http cookie header fields, see http://tools.ietf.org/html/rfc6265 This class is sealed abstract to prevent generation of default apply method in companion
Support class for building user-defined custom headers defined by implementing name
and value
.
Support class for building user-defined custom headers defined by implementing name
and value
.
By implementing a ModeledCustomHeader instead of CustomHeader directly, all needed unapply
methods are provided for this class, such that it can be pattern matched on from RawHeader and
the other way around as well.
To be extended by companion object of a custom header extending ModeledCustomHeader.
To be extended by companion object of a custom header extending ModeledCustomHeader. Implements necessary apply and unapply methods to make the such defined header feel "native".
A websocket extension as defined in http://tools.ietf.org/html/rfc6455#section-4.3
De-facto standard as per https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Host
De-facto standard as per https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Host
de-facto standard as per https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto
de-facto standard as per https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Forwarded-Proto
Document http://tools.ietf.org/html/rfc6266 updates document https://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html.
Document http://tools.ietf.org/html/rfc6266 updates document https://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html. Between these two there is slight but important difference regarding how parameter values are formatted. In RFC6266 parameters values are without quotes and in RFC2616 they are quoted. Since common practice among http servers is to understand quoted values, we use older document as reference here.
Model for the synthetic Tls-Session-Info
header which carries the SSLSession of the connection
the message carrying this header was received with.
Model for the synthetic Tls-Session-Info
header which carries the SSLSession of the connection
the message carrying this header was received with.
This header will only be added if it enabled in the configuration by setting
akka.http.[client|server].parsing.tls-session-info-header = on