Hi,
We are using nginx as reverse proxy and have a set of upstream servers
configured
with upstream next enabled for few error conditions to try next upstream
server.
For some reason this is not working. Can someone suggest if am missing
something?
http {
...
upstream myservice {
server loc
On Tue, 14 Feb 2017, Eran Kornblau wrote:
If I understand your description correctly, I had the same problem - I wanted
to expose an internal error code
of my module as an nginx variable, so that I could write it to the access log.
But after the redirect to the error page,
the context was er
If I understand your description correctly, I had the same problem - I wanted
to expose an internal error code
of my module as an nginx variable, so that I could write it to the access log.
But after the redirect to the error page,
the context was erased and the handler could not retrieve it.
T
Hello,
On Tue, Feb 14, 2017 at 07:25:49AM -0800, Pillai, Saju wrote:
>
> Hello,
>
> I am new to nginx and will appreciate some insight on handling the resetting
> of
> module ctx during internal redirects.
>
> Specifically, I have a module that runs in the HTTP_POST_READ_PHASE to build
> some
details: http://hg.nginx.org/nginx/rev/d99a7f0062ad
branches:
changeset: 6912:d99a7f0062ad
user: Maxim Dounin
date: Tue Feb 14 18:36:04 2017 +0300
description:
release-1.11.10 tag
diffstat:
.hgtags | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs (8 lines):
diff --
details: http://hg.nginx.org/nginx/rev/1ad0999a7ded
branches:
changeset: 6911:1ad0999a7ded
user: Maxim Dounin
date: Tue Feb 14 18:36:04 2017 +0300
description:
nginx-1.11.10-RELEASE
diffstat:
docs/xml/nginx/changes.xml | 102 +
1 files
Hello,
I am new to nginx and will appreciate some insight on handling the resetting of
module ctx during internal redirects.
Specifically, I have a module that runs in the HTTP_POST_READ_PHASE to build
some objects in memory, which it hangs off the request object via
ngx_http_set_ctx(r,..). The
Thanks a lot for your reply.
So we can regard the patch is right, but it's not recommended.
Because it's more easily to break the request behavior in limiting rate.
And the limit_rate variable is also deprecated though it's so useful
that we can dynamically change the rate.
2017-02-14 21:11 GMT+0
Hello!
On Tue, Feb 14, 2017 at 03:54:35PM +0800, 洪志道 wrote:
> Dose nginx consider support setting variable about limit_rate_after?
> We can limit rate after $n bytes received from upstream.
No. A patch to introduce the $limit_rate_after variable was made
several years ago, see this ticket:
ht
