error_page and module contexts

[Dave Bailey]

Hi,

On Fri, Feb 3, 2012 at 9:52 AM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Fri, Feb 03, 2012 at 08:53:26AM -0800, Dave Bailey wrote:
>
> > Hi,
> >
> > As of nginx 1.1.6, it seems that the error_page directive can no longer
> be
> > used in a way that preserves module contexts to the log phase of the
> > request cycle.  This means that if I have a log handler which expects
> some
> > information that had been saved in a module context before the error_page
> > logic is invoked, that information is no longer accessible when the log
> > handler is actually called.  Is there a way to work around this?
>
> Currently the only thing which survives internal redirects (and
> redirection to a named location as of 1.1.6+) is variables.  If
> you need something persistant, you may register one and store
> needed information there (up to a pointer to your module context,
> actually).
>

Great, thank you.  Looks like this will work perfectly.


> Maxim Dounin
>
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
>

-dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20120203/c5f97239/attachment.html>