On Wednesday 11 November 2015 13:17:47 Julien FROMENT wrote:
> Using post_action could work, if we can sent to the @after_request_location
> enough reliable information.
[..]
Using "access_log syslog" for this purpose will be much better solution.
See the http_log module documentation for detai
Brester (sebres)
> FROM: Sergey Brester [mailto:serg.bres...@sebres.de]
> SENT: Tuesday, November 10, 2015 2:30 PM
> TO: nginx-devel@nginx.org
> CC: Julien FROMENT
> SUBJECT: Re: Tracking sent responses
>
> Hi,
>
> I'm sure you can do that using on-board &
, November 10, 2015 2:30 PM
To: nginx-devel@nginx.org
Cc: Julien FROMENT
Subject: Re: Tracking sent responses
Hi,
I'm sure you can do that using on-board "equipment" of nginx, without deep
integrating to the nginx (without write of own module).
You can use for this a "pos
Hi,
I'm sure you can do that using on-board "equipment" of nginx, without
deep integrating to the nginx (without write of own module).
You can use for this a "post_action", something like:
post_action @after_request_location;
But (There is always a "but":), according to my last known sta
