On Tue, Jan 20, 2015 at 11:46:36AM +0100, Jan Algermissen wrote:
> On 19 Jan 2015, at 21:38, Francis Daly wrote:
> > Completely untested, but, depending on how you connect to upstream, does
> > "proxy_hide_header" or "proxy_ignore_headers" do what you want?
>
> Do you have any idea, how I can th
On 19 Jan 2015, at 21:38, Francis Daly wrote:
> On Mon, Jan 19, 2015 at 08:44:33PM +0100, Jan Algermissen wrote:
>
> Hi there,
>
>> upstream U1 produces the main page (the one containing SSI include
>> directives) and wants nginx to cache its response (the page with the
>> unresolved SSI inc
Jan Algermissen Wrote:
---
> Francis,
>
> thanks a lot;
>
> > proxy_hide_header
>
> does the trick. However, it still feels a bit brute-force.
>
> Hence, if there are other solutions, I would be curious to know.
With Lua you could test to se
Francis,
thanks a lot;
> proxy_hide_header
does the trick. However, it still feels a bit brute-force.
Hence, if there are other solutions, I would be curious to know.
Meanwhile, “hide” gets me going.
Jan
On 19 Jan 2015, at 21:38, Francis Daly wrote:
> On Mon, Jan 19, 2015 at 08:44:33PM +0
On Mon, Jan 19, 2015 at 08:44:33PM +0100, Jan Algermissen wrote:
Hi there,
> upstream U1 produces the main page (the one containing SSI include
> directives) and wants nginx to cache its response (the page with the
> unresolved SSI include directives). Thus U1 sends the main page with
> Cache-
Hi,
[apologies if this has been asked lots of times before, but searches really did
not turn up anything]
I am using nginx with SSI enabled to assemble pages and page-fragments from
upstream servers.
upstream U1 produces the main page (the one containing SSI include directives)
and wants ngin
