No headers filter for a subrequest

[Marat Dakota]

Well, my problem is that I need these headers (I eat them from my module's
header filter).
I use subrequests for API calls. Does this mean that subrequests are the
wrong way to do so? Do I need to use upstreams instead?


On Mon, Mar 16, 2015 at 3:39 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Mon, Mar 16, 2015 at 03:32:30PM +0300, Marat Dakota wrote:
>
> > I also might have:
> >
> > /location3 {
> >     proxy_pass https://www.blabla;
> > }
> >
> > In this case my subrequest has the response headers from www.blabla. This
> > means that the statement that there are no headers in subrequest
> responses
> > is not completely correct.
>
> In either case headers returned to the client are ones returned by
> the main request.  Anything else, if present for some unrelated
> reasons, will be thrown away.
>
> [...]
>
> --
> Maxim Dounin
> http://nginx.org/
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20150316/8560a931/attachment.html>