package values

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. Protected

Type Members

  1. sealed trait Accept extends AnyRef

    Accept header value.

  2. sealed trait AcceptEncoding extends AnyRef

    Represents an AcceptEncoding header value.

  3. sealed trait AcceptLanguage extends AnyRef

    The Accept-Language request HTTP header indicates the natural language and locale that the client prefers.

  4. sealed trait AcceptPatch extends AnyRef

    The Accept-Patch response HTTP header advertises which media-type the server is able to understand in a PATCH request.

  5. sealed trait AcceptRanges extends AnyRef

    The Accept-Ranges HTTP response header is a marker used by the server to advertise its support for partial requests from the client for file downloads.

    The Accept-Ranges HTTP response header is a marker used by the server to advertise its support for partial requests from the client for file downloads. The value of this field indicates the unit that can be used to define a range. By default the RFC 7233 specification supports only 2 possible values.

  6. sealed trait AccessControlAllowCredentials extends AnyRef
  7. sealed trait AccessControlAllowHeaders extends AnyRef
  8. sealed trait AccessControlAllowMethods extends AnyRef
  9. sealed trait AccessControlAllowOrigin extends AnyRef

    The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin.

    The Access-Control-Allow-Origin response header indicates whether the response can be shared with requesting code from the given origin.

    For requests without credentials, the literal value "*" can be specified as a wildcard; the value tells browsers to allow requesting code from any origin to access the resource. Attempting to use the wildcard with credentials results in an error.

    <origin> Specifies an origin. Only a single origin can be specified. If the server supports clients from multiple origins, it must return the origin for the specific client making the request.

    null Specifies the origin "null".

  10. sealed trait AccessControlExposeHeaders extends AnyRef

    The Access-Control-Expose-Headers response header allows a server to indicate which response headers should be made available to scripts running in the browser, in response to a cross-origin request.

  11. sealed trait AccessControlMaxAge extends AnyRef

    The Access-Control-Max-Age response header indicates how long the results of a preflight request (that is the information contained in the Access-Control-Allow-Methods and Access-Control-Allow-Headers headers) can be cached.

    The Access-Control-Max-Age response header indicates how long the results of a preflight request (that is the information contained in the Access-Control-Allow-Methods and Access-Control-Allow-Headers headers) can be cached.

    Maximum number of seconds the results can be cached, as an unsigned non-negative integer. Firefox caps this at 24 hours (86400 seconds). Chromium (prior to v76) caps at 10 minutes (600 seconds). Chromium (starting in v76) caps at 2 hours (7200 seconds). The default value is 5 seconds.

  12. sealed trait AccessControlRequestHeaders extends AnyRef
  13. sealed trait AccessControlRequestMethod extends AnyRef
  14. sealed trait Age extends AnyRef

    Age header value.

  15. sealed trait Allow extends AnyRef

    The Allow header must be sent if the server responds with a 405 Method Not Allowed status code to indicate which request methods can be used.

  16. sealed trait AuthenticationScheme extends AnyRef
  17. sealed trait Authorization extends AnyRef

    Authorization header value.

  18. sealed trait CacheControl extends AnyRef

    CacheControl header value.

  19. sealed trait Connection extends AnyRef

    Connection header value.

  20. sealed trait ContentBase extends AnyRef
  21. sealed trait ContentDisposition extends AnyRef
  22. sealed trait ContentEncoding extends AnyRef
  23. sealed trait ContentLanguage extends AnyRef
  24. sealed trait ContentLength extends AnyRef

    ContentLength header value

  25. sealed trait ContentLocation extends AnyRef
  26. sealed trait ContentMd5 extends AnyRef
  27. sealed trait ContentRange extends AnyRef
  28. sealed trait ContentSecurityPolicy extends AnyRef
  29. sealed trait ContentTransferEncoding extends AnyRef
  30. sealed trait ContentType extends Product with Serializable
  31. sealed trait DNT extends AnyRef
  32. sealed trait Date extends AnyRef
  33. sealed trait ETag extends AnyRef
  34. sealed trait Expect extends AnyRef

    The Expect HTTP request header indicates expectations that need to be met by the server to handle the request successfully.

    The Expect HTTP request header indicates expectations that need to be met by the server to handle the request successfully. There is only one defined expectation: 100-continue

  35. sealed trait Expires extends AnyRef
  36. sealed trait From extends AnyRef

    From header value.

  37. sealed trait Host extends AnyRef
  38. sealed trait IfMatch extends AnyRef
  39. sealed trait IfModifiedSince extends AnyRef
  40. sealed trait IfNoneMatch extends AnyRef
  41. sealed trait IfRange extends AnyRef

    The If-Range HTTP request header makes a range request conditional.

    The If-Range HTTP request header makes a range request conditional. Possible values:

    • <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT
    • <etag> a string of ASCII characters placed between double quotes (Like "675af34563dc-tr34"). A weak entity tag (one prefixed by W/) must not be used in this header.
  42. sealed trait IfUnmodifiedSince extends AnyRef
  43. sealed trait LastModified extends AnyRef
  44. sealed trait Location extends AnyRef

    Location header value.

  45. sealed trait MaxForwards extends AnyRef

    Max-Forwards header value

  46. sealed trait Origin extends AnyRef

    Origin header value.

  47. sealed trait Pragma extends AnyRef

    Pragma header value.

  48. sealed trait ProxyAuthenticate extends AnyRef

    The HTTP Proxy-Authenticate response header defines the authentication method that should be used to gain access to a resource behind a proxy server.

    The HTTP Proxy-Authenticate response header defines the authentication method that should be used to gain access to a resource behind a proxy server. It authenticates the request to the proxy server, allowing it to transmit the request further.

  49. sealed trait ProxyAuthorization extends AnyRef
  50. sealed trait Range extends AnyRef
  51. sealed trait Referer extends AnyRef

    The Referer HTTP request header contains the absolute or partial address from which a resource has been requested.

    The Referer HTTP request header contains the absolute or partial address from which a resource has been requested. The Referer header allows a server to identify referring pages that people are visiting from or where requested resources are being used. This data can be used for analytics, logging, optimized caching, and more.

    When you click a link, the Referer contains the address of the page that includes the link. When you make resource requests to another domain, the Referer contains the address of the page that uses the requested resource.

    The Referer header can contain an origin, path, and querystring, and may not contain URL fragments (i.e. #section) or username:password information. The request's referrer policy defines the data that can be included. See Referrer-Policy for more information and examples.

  52. sealed trait RequestCookie extends AnyRef
  53. sealed trait ResponseCookie extends AnyRef
  54. sealed trait RetryAfter extends AnyRef
  55. sealed trait SecWebSocketAccept extends AnyRef
  56. sealed trait SecWebSocketExtensions extends AnyRef
  57. sealed trait SecWebSocketKey extends AnyRef
  58. sealed trait SecWebSocketLocation extends AnyRef
  59. sealed trait SecWebSocketOrigin extends AnyRef
  60. sealed trait SecWebSocketProtocol extends AnyRef
  61. sealed trait SecWebSocketVersion extends AnyRef
  62. sealed trait Server extends AnyRef

    Server header value.

  63. sealed trait Te extends AnyRef
  64. sealed trait Trailer extends AnyRef

    Trailer header value.

  65. sealed trait TransferEncoding extends AnyRef
  66. sealed trait Upgrade extends AnyRef
  67. sealed trait UpgradeInsecureRequests extends AnyRef
  68. sealed trait UserAgent extends AnyRef
  69. sealed trait Vary extends AnyRef

    Vary header value.

  70. sealed trait Via extends AnyRef
  71. sealed trait WWWAuthenticate extends AnyRef
  72. sealed trait Warning extends AnyRef
  73. sealed trait XFrameOptions extends AnyRef
  74. sealed trait XRequestedWith extends AnyRef

Value Members

  1. object Accept
  2. object AcceptEncoding
  3. object AcceptLanguage
  4. object AcceptPatch
  5. object AcceptRanges
  6. object AccessControlAllowCredentials
  7. object AccessControlAllowHeaders

    The Access-Control-Allow-Headers response header is used in response to a preflight request which includes the Access-Control-Request-Headers to indicate which HTTP headers can be used during the actual request.

  8. object AccessControlAllowMethods
  9. object AccessControlAllowOrigin
  10. object AccessControlExposeHeaders
  11. object AccessControlMaxAge
  12. object AccessControlRequestHeaders

    The Access-Control-Request-Headers request header is used by browsers when issuing a preflight request to let the server know which HTTP headers the client might send when the actual request is made (such as with setRequestHeader()).

    The Access-Control-Request-Headers request header is used by browsers when issuing a preflight request to let the server know which HTTP headers the client might send when the actual request is made (such as with setRequestHeader()). The complementary server-side header of Access-Control-Allow-Headers will answer this browser-side header.

  13. object AccessControlRequestMethod
  14. object Age
  15. object Allow
  16. object AuthenticationScheme
  17. object Authorization
  18. object CacheControl
  19. object Connection
  20. object ContentBase
  21. object ContentDisposition
  22. object ContentEncoding
  23. object ContentLanguage
  24. object ContentLength
  25. object ContentLocation
  26. object ContentMd5
  27. object ContentRange
  28. object ContentSecurityPolicy
  29. object ContentTransferEncoding
  30. object ContentType extends Serializable
  31. object DNT
  32. object Date

    The Date general HTTP header contains the date and time at which the message originated.

  33. object ETag
  34. object Expect
  35. object Expires

    The Expires HTTP header contains the date/time after which the response is considered expired.

    The Expires HTTP header contains the date/time after which the response is considered expired.

    Invalid expiration dates with value 0 represent a date in the past and mean that the resource is already expired.

    Expires: <Date>

    Date: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT

    Example:

    Expires: Wed, 21 Oct 2015 07:28:00 GMT

  36. object From
  37. object Host
  38. object IfMatch
  39. object IfModifiedSince
  40. object IfNoneMatch
  41. object IfRange
  42. object IfUnmodifiedSince

    If-Unmodified-Since request header makes the request for the resource conditional: the server will send the requested resource or accept it in the case of a POST or another non-safe method only if the resource has not been modified after the date specified by this HTTP header.

  43. object LastModified
  44. object Location
  45. object MaxForwards
  46. object Origin
  47. object Pragma
  48. object ProxyAuthenticate
  49. object ProxyAuthorization

    The HTTP Proxy-Authorization request header contains the credentials to authenticate a user agent to a proxy server, usually after the server has responded with a 407 Proxy Authentication Required status and the Proxy-Authenticate header.

  50. object Range
  51. object Referer
  52. object RequestCookie

    The Cookie HTTP request header contains stored HTTP cookies associated with the server.

  53. object ResponseCookie
  54. object RetryAfter

    The RetryAfter HTTP header contains the date/time after which to retry

    The RetryAfter HTTP header contains the date/time after which to retry

    Invalid RetryAfter with value 0

    RetryAfter: <Date>

    Date: <day-name>, <day> <month> <year> <hour>:<minute>:<second> GMT

    Example:

    Expires: Wed, 21 Oct 2015 07:28:00 GMT

    Or RetryAfter the delay seconds.

  55. object SecWebSocketAccept

    The Sec-WebSocket-Accept header is used in the websocket opening handshake.

    The Sec-WebSocket-Accept header is used in the websocket opening handshake. It would appear in the response headers. That is, this is header is sent from server to client to inform that server is willing to initiate a websocket connection.

    See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-WebSocket-Accept

  56. object SecWebSocketExtensions

    The Sec-WebSocket-Extensions header is used in the WebSocket handshake.

    The Sec-WebSocket-Extensions header is used in the WebSocket handshake. It is initially sent from the client to the server, and then subsequently sent from the server to the client, to agree on a set of protocol-level extensions to use during the connection.

    See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-WebSocket-Extensions

  57. object SecWebSocketKey

    The Sec-WebSocket-Key header is used in the WebSocket handshake.

    The Sec-WebSocket-Key header is used in the WebSocket handshake. It is sent from the client to the server to provide part of the information used by the server to prove that it received a valid WebSocket handshake. This helps ensure that the server does not accept connections from non-WebSocket clients (e.g. HTTP clients) that are being abused to send data to unsuspecting WebSocket servers.

    See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-WebSocket-Key

  58. object SecWebSocketLocation
  59. object SecWebSocketOrigin

    The Sec-WebSocket-Origin header is used to protect against unauthorized cross-origin use of a WebSocket server by scripts using the |WebSocket| API in a Web browser.

    The Sec-WebSocket-Origin header is used to protect against unauthorized cross-origin use of a WebSocket server by scripts using the |WebSocket| API in a Web browser. The server is informed of the script origin generating the WebSocket connection request.

  60. object SecWebSocketProtocol

    The Sec-WebSocket-Protocol header field is used in the WebSocket opening handshake.

    The Sec-WebSocket-Protocol header field is used in the WebSocket opening handshake. It is sent from the client to the server and back from the server to the client to confirm the subprotocol of the connection. This enables scripts to both select a subprotocol and be sure that the server agreed to serve that subprotocol.

    See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-WebSocket-Protocol

  61. object SecWebSocketVersion

    The Sec-WebSocket-Version header field is used in the WebSocket opening handshake.

    The Sec-WebSocket-Version header field is used in the WebSocket opening handshake. It is sent from the client to the server to indicate the protocol version of the connection.

    See: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-WebSocket-Version

  62. object Server
  63. object Te
  64. object Trailer
  65. object TransferEncoding
  66. object Upgrade
  67. object UpgradeInsecureRequests

    The HTTP Upgrade-Insecure-Requests request header sends a signal to the server expressing the client's preference for an encrypted and authenticated response.

  68. object UserAgent

    The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user agent limitations, and for analytics regarding browser or operating system use

  69. object Vary
  70. object Via

    The Via general header is added by proxies, both forward and reverse, and can appear in the request or response headers.

    The Via general header is added by proxies, both forward and reverse, and can appear in the request or response headers. It is used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities of senders along the request/response chain

  71. object WWWAuthenticate
  72. object Warning
  73. object XFrameOptions
  74. object XRequestedWith

Ungrouped