Restrictions to modifying request->headers_in.headers in NGX_HTTP_PREACCESS_PHASE?

[Robert Paprocki]

Hello,

On Thu, Mar 29, 2018 at 11:06 AM, Ryan Burn <rnickb731 at gmail.com> wrote:
>
>
> This module injects multiple headers and the number, keys, etc aren't
> meant to be exposed to the user.
>
> (This module is mean to support tracing and the injected headers btw
> correspond to a SpanContext:
> http://opentracing.io/documentation/pages/api/cross-process-tracing.html
> which varies by the trace used).
>
> Is there way to accomplish this without having the configuration
> author do anything?
>


What's the source of these header names/values? If it's passed from the
downstream client, it will automatically be proxied to the upstream server
(with some exceptions, see the proxy module documentation).

If it's generated on the Nginx node itself, you should be able to use the
proxy_set_header Maxim defined above, in combination with variables which
could be generated via your custom module or some other approach.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20180329/7447503a/attachment-0001.html>