Hi guys,
since I cannot login into trac (no OAuth handler found), I'll try reporting
it here. We are experiencing segmentation faults on nginx 1.16.1 with
post_action.
CentOS:
# cat /etc/centos-release
CentOS Linux release 7.6.1810 (Core)
Nginx:
# nginx -V
nginx version: nginx/1.16.1
bui
Hi, jacks.
I use post_action for something similar to this for keeping track of users
who download files. I've got a location for the /download entry point like
this:
location ~ /download/ {
proxy_pass http://app_pool;
proxy_set_header Host $host;
proxy_set_header X-Re
On Tue, Dec 03, 2019 at 04:48:23AM -0500, jacks wrote:
Hi there,
since no-one else has answered this yet...
> What am i doing wrong?
Without me trying to be clever about it: you're asking for help about
post_action.
I think that the post_action directive is only documented in
Hi
I am trying to configure NGINX to send another http request after successful
completion of the original proxied request, in order to count statistics
etc'
I am using post_action with proxy_pass as following:
location / {
proxy_http_version 1.1;
proxy_set_header
The post_action in the config for my Nginx 1.12.1 instance is not firing (or
does not appear to be). I'm wondering if it is because my app server is
returning a X-Accel-Redirect header. The ultimate goal is track when
downloads hosted on S3 have completed.
Step 1: The request hits ngi
v1.4.6
I'm attempting to proxy pass requests to AWS API Gateway, but they are not
reaching the endpoint. Example of my configuration below. Requests come
through as something like some.domain.com/some_resource
The final post_action hop at the bottom is attempting to pass the request
an
Hi All,
As post_action is no longer documented could someone tell me if post_action
will be dropped from future releases, should I use it?
Thanks.
Jonathan
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello!
On Wed, Jun 14, 2017 at 05:52:09PM -0400, wonderer wrote:
> Hi All,
>
> To start with, here's some context. From what i've read around, the
> post_action directive is to be used with caution. I was able to find this
> information following the lin
Hi All,
To start with, here's some context. From what i've read around, the
post_action directive is to be used with caution. I was able to find this
information following the link from this post:
https://forum.nginx.org/read.php?2,262008,262012#msg-262012
I also found documentat
Ok, thanks for the link.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,262008,262107#msg-262107
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
I've found this archive explaining why it's not in the documentation:
http://mailman.nginx.org/pipermail/nginx/2012-November/036199.html
Best Regards
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,262008,262012#msg-262012
___
nginx m
Hello.
I can't find description for "post_action" in documentation.
Earlier (in static version of documentation) was description of this
directive.
This directive is still actual?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,262008,26
Hi, i'm using post_action for remote logging. Logging all requests works
great and efficient (4k req/s) but when I try to log only certain requests
ngix becomes unstable (some connections hang and some weird errors occur).
I've tried several ways to log specific requests only, but no
As Maxim pointed out specifically in a not-that-old message, the
'post_action' directive is left undocumented on purpose, since it implies
carefulness and knowledge to manipulate properly.
Although my request might seem naive to certain people, wouldn't it be more
profitable
14 matches
Mail list logo
