Feature description
Goal: Details about how HTTP message signatures work behind load balancers / TLS-terminating proxies
Provide adequate technical acceptance criteria(s) associated with this feature below:
- Details about how HTTP message signatures work behind load balancers / TLS-terminating proxies
- Specify how verifiers reconstruct the signed target (e.g.,
Forwarded/X-Forwarded-* precedence) or switch to signing @path, otherwise signatures will break when host/scheme are rewritten.
Although not required, it is highly encouraged to provide feature use-cases below:
Main use case is to increase viability and maturity of the Margo management interface. Enables the API to be utilized in cloud environments enabling scaling and security layers.
Additional information
- New assumption is PR to spec to enhance already approved strategies
Feature description
Goal: Details about how HTTP message signatures work behind load balancers / TLS-terminating proxies
Provide adequate technical acceptance criteria(s) associated with this feature below:
Forwarded/X-Forwarded-*precedence) or switch to signing@path, otherwise signatures will break when host/scheme are rewritten.Although not required, it is highly encouraged to provide feature use-cases below:
Main use case is to increase viability and maturity of the Margo management interface. Enables the API to be utilized in cloud environments enabling scaling and security layers.
Additional information