Bumping; does anyone have experience using upstream_bytes_sent or
upstream_byes_received?
On Tue, Apr 25, 2017 at 2:53 PM Chad Hansen wrote:
> I'm running nginx 1.11.9, and I get an error any time I try to use
> bytes_sent, upstream_bytes_sent, or upstream_bytes_received. I've
I'm running nginx 1.11.9, and I get an error any time I try to use
bytes_sent, upstream_bytes_sent, or upstream_bytes_received. I've tried
logging directly in a log format, or using in a map:
map $request_method $chad_sent {
default $upstream_bytes_sent;
}
map $request_method $chad_received {
gic I needed to use openresty,
> which is an nginx bundle that adds a lot of customization points.
>
> Sent from my iPhone
>
> > On Feb 8, 2017, at 5:47 PM, Chad Hansen via nginx
> wrote:
> >
> > I use nginx as a reverse proxy, and upstream clients have a need for my
I use nginx as a reverse proxy, and upstream clients have a need for my
service to cache differently than downstream servers.
Is there a way to change what header nginx uses to accept cache settings?
Or a way to re-write cache headers before the cache settings take affect?
For example, I could ha
Great, thank you!
On Thu, Jul 14, 2016 at 4:26 PM Maxim Dounin wrote:
> Hello!
>
> On Thu, Jul 14, 2016 at 07:22:06PM +0000, Chad Hansen wrote:
>
> > I'm looking for documentation or explanation for how keys expire in the
> > limit_req_zone. I have the basic d
I'm looking for documentation or explanation for how keys expire in the
limit_req_zone. I have the basic documenations here:
*A client IP address serves as a key. Note that instead of $remote_addr,
the $binary_remote_addr variable is used here.
The $binary_remote_addr variable’s size is always 4 b
