The l5d-ctx-deadline
header propagates a request
deadline.
The l5d-ctx-deadline
header propagates a request
deadline. Each router server may use this deadline to cancel or
reject work.
Each router client sets a deadline that it is at least as strict as the deadline it received. If an incoming request has a deadline, the outgoing request MUST have a deadline. Otherwise, outgoing requests MAY have a deadline.
There are two headers used to control local Dtabs in linkerd:
There are two headers used to control local Dtabs in linkerd:
l5d-ctx-dtab
is read and _written_ by linkerd. It is
intended to managed entirely by linkerd, and applications
should only forward requests prefixed by l5d-ctx-*
. *NOTE*: the client module does not yet encode
l5d-ctx-dtab
. dtab-local
is still to be relied on
until https://github.com/twitter/finagle/pull/514 is
complete.
2. l5d-dtab
is to be provided by users. Applications are
not required to forward l5d-dtab
when fronted by
linkerd.
l5d-dtab
is appended to l5d-ctx-dtab
, so that user-provided
delegations take precdence.
A clientside stack module that injects local contextual information onto downstream requests.
A clientside stack module that injects local contextual information onto downstream requests. Currently this includes:
Note that Dtabs are *not* encoded by this filter, since the
HttpClientDispatcher is currently responsible for encoding the
dtab-local
header. In a future release, Dtabs will be encoded
into the l5d-ctx-dtab
header.
Note that trace configuration is handled by HttpTraceInitializer.clientModule.
A serverside stack module that extracts contextual information
from requests and configures the local
com.twitter.finagle.Context
appropriately.
A serverside stack module that extracts contextual information
from requests and configures the local
com.twitter.finagle.Context
appropriately. Currently this includes:
Note that currently, the dtabs read by this module are
appeneded to that specified by the l5d-dtab
header. The
dtab-local
header should be considered deprecated in favor of
l5d-dtab
, and will not be supported in the future.
Note that trace configuration is handled by HttpTraceInitializer.serverModule.