Constants

HTTP header key age. Gives the current age of a cached HTTP response.

Represents the Authorization header name.

The prefix used to denote the Basic authentication scheme.

The prefix used to denote the Bearer authentication scheme.

HTTP header key authorization

HTTP header key cache-control. Specifies the cache control directives required for the function of HTTP caches.

This is a more restricted mode of RFC 7234. Setting this as the caching policy restricts caching to instances where the cache-control header and either the etag or last-modified header are present.

Represents the closed state of the circuit. When the Circuit Breaker is in CLOSED state, all requests will be allowed to go through to the upstream service. If the failures exceed the configured threhold values, the circuit will trip and move to the OPEN state.

Represents the half-open state of the circuit. When the Circuit Breaker is in HALF_OPEN state, a trial request will be sent to the upstream service. If it fails, the circuit will trip again and move to the OPEN state. If not, it will move to the CLOSED state.

Represents the open state of the circuit. When the Circuit Breaker is in OPEN state, requests will fail immediately.

Always set chunking header in the response.

If the payload is less than 8KB, content-length header is set in the outbound request/response, otherwise chunking header is set in the outbound request/response.}

Never set the chunking header even if the payload is larger than 8KB in the outbound request/response.

Always set accept-encoding/content-encoding in outbound request/response.

When service behaves as a HTTP gateway inbound request/response accept-encoding option is set as the outbound request/response accept-encoding/content-encoding option.

Never set accept-encoding/content-encoding header in outbound request/response.

HTTP header key connection. Allows the sender to specify options that are desired for that particular connection.

HTTP header key content-length. Specifies the size of the response body in bytes.

HTTP header key content-type. Specifies the type of the message payload.

HTTP header key date. The timestamp at the time the response was generated/received.

HTTP header key etag. A finger print for a resource which is used by HTTP caches to identify whether a resource representation has changed.

HTTP header key expect. Specifies expectations to be fulfilled by the server.

HTTP header key expires. Specifies the time at which the response becomes stale.

Mutual SSL handshake has failed.

Constant for the HTTP DELETE method

Constant for the HTTP FORWARD method

Constant for the HTTP GET method

Constant for the HTTP HEAD method

Constant for the identify not an HTTP Operation

Constant for the HTTP OPTIONS method

Constant for the HTTP PATCH method

Constant for the HTTP POST method

Constant for the HTTP PUT method

constant for the HTTP SUBMIT method

HTTP header key if-match

HTTP header key if-modified-since. Used when validating (with the origin server) whether a cached response is still valid. If the representation of the resource has modified since the timestamp in this field, a 304 response is returned.

HTTP header key if-none-match. Used when validating (with the origin server) whether a cached response is still valid. If the ETag provided in this field matches the representation of the requested resource, a 304 response is returned.

HTTP header key if-range

HTTP header key if-unmodified-since

Keeps the connection alive irrespective of the connection header value }

Decides to keep the connection alive or not based on the connection header of the client request }

Closes the connection irrespective of the connection header value }

HTTP header key last-modified. The time at which the resource was last modified.

Header is placed before the payload of the request/response.

HTTP header key location. Indicates the URL to redirect a request to.

When used in requests, max-age implies that clients are not willing to accept responses whose age is greater than max-age. When used in responses, the response is to be considered stale after the specified number of seconds.

Indicates that the client is willing to accept responses which have exceeded their freshness lifetime by no more than the specified number of seconds.

Setting this as the max-stale directives indicates that the max-stale directive does not specify a limit.

Indicates that the client is only accepting responses whose freshness lifetime >= current age + min-fresh.

Represents multipart primary type

Indicates that once the response has become stale, it should not be reused for subsequent requests without validating with the origin server.

Forces the cache to validate a cached response with the origin server before serving.

Instructs the cache to not store a response in non-volatile storage.

Instructs intermediaries not to transform the payload.

Not a mutual ssl connection.

Indicates that the client is only willing to accept a cached response. A cached response is served subject to other constraints posed by the request.

Mutual SSL handshake is successful.

HTTP header key pragma. Used in dealing with HTTP 1.0 caches which do not understand the cache-control header.

Indicates that the response is intended for a single user and should not be stored by shared caches.

HTTP header key proxy-authorization. Contains the credentials to authenticate a user agent to a proxy serve.

Has the same semantics as must-revalidate, except that this does not apply to private caches.

Indicates that any cache may store the response.

Represents the HTTP redirect status code 302 - Found.

Represents the HTTP redirect status code 301 - Moved Permanently.

Represents the HTTP redirect status code 300 - Multiple Choices.

Represents the HTTP redirect status code 304 - Not Modified.

Represents the HTTP redirect status code 308 - Permanent Redirect.

Represents the HTTP redirect status code 303 - See Other.

Represents the HTTP redirect status code 307 - Temporary Redirect.

Represents the HTTP redirect status code 305 - Use Proxy.

Constant for the request method reference.

Constant for the resource name reference.

Caching behaviour is as specified by the RFC 7234 specification.

In shared caches, s-maxage overrides the max-age or expires header field.

HTTP header key server. Specifies the details of the origin server.

Constant for the service name reference.

The HTTP response status code: 202 Accepted

The HTTP response status code: 502 Bad Gateway

The HTTP response status code: 400 Bad Request

The HTTP response status code: 409 Conflict

The HTTP response status code: 100 Continue

The HTTP response status code: 201 Created

The HTTP response status code: 417 Expectation Failed

The HTTP response status code: 403 Forbidden

The HTTP response status code: 302 Found

The HTTP response status code: 504 Gateway Timeout

The HTTP response status code: 410 Gone

The HTTP response status code: 505 HTTP Version Not Supported

The HTTP response status code: 500 Internal Server Error

The HTTP response status code: 411 Length Required

The HTTP response status code: 405 Method Not Allowed

The HTTP response status code: 301 Moved Permanently

The HTTP response status code: 300 Multiple Choices

The HTTP response status code: 204 No Content

The HTTP response status code: 203 Non Authoritative Information

The HTTP response status code: 406 Not Acceptable

The HTTP response status code: 404 Not Found

The HTTP response status code: 501 Not Implemented

The HTTP response status code: 304 Not Modified

The HTTP response status code: 200 OK

The HTTP response status code: 206 Partial Content

The HTTP response status code: 413 Payload Too Large

The HTTP response status code: 402 Payment Required

The HTTP response status code: 308 Permanent Redirect

The HTTP response status code: 412 Precondition Failed

The HTTP response status code: 407 Proxy Authentication Required

The HTTP response status code: 416 Range Not Satisfiable

The HTTP response status code: 431 Request Header Fields Too Large

The HTTP response status code: 408 Request Timeout

The HTTP response status code: 205 Reset Content

The HTTP response status code: 303 See Other

The HTTP response status code: 503 Service Unavailable

The HTTP response status code: 101 Switching Protocols

The HTTP response status code: 307 Temporary Redirect

The HTTP response status code: 401 Unauthorized

The HTTP response status code: 415 Unsupported Media Type

The HTTP response status code: 426 Upgrade Required

The HTTP response status code: 414 URI Too Long

The HTTP response status code: 305 Use Proxy

Header is placed after the payload of the request/response.

HTTP header key transfer-encoding. Specifies what type of transformation has been applied to entity body.

HTTP header key upgrade. Allows the client to specify what additional communication protocols it supports and would like to use, if the server finds it appropriate to switch protocols.

HTTP header key warning. Specifies warnings generated when serving stale responses from HTTP caches.