[Nitro] mod_proxy and 404's

George Moschovitis george.moschovitis at gmail.com
Wed Jan 31 13:02:23 EST 2007


This is fixed in the repository version of Nitro. In fact the repository
version uses different templates for 4xx and 5xx errors.

-g.

On 1/31/07, nitrojesus.5.pistos at geoshell.com <
nitrojesus.5.pistos at geoshell.com> wrote:
>
> On 31/01/07, Jonathan Buch - john at oxyliquit.de wrote:
> > On Wed, 31 Jan 2007 06:50:58 +0100, <nitrojesus.5.pistos at geoshell.com>
> wrote:
> >
> > > On 29/01/07, George Moschovitis - george.moschovitis at gmail.com wrote:
> > >>     @context.status = 400
> > > See attached minimal demo application.  The index page gives a 404
> > > just fine, but it's the *error* page that doesn't.
> > error.xhtml sets the error code to 500 by hand.
>
> Using Firefox's Webdeveloper plugin to look at the response headers, I
> can see that I can set @context.status to 404 from my index action,
> but in the error action, it does not take effect (or gets overridden
> with later code outside of my application).
>
> I've never seen 500.
>
> Pistos
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>



-- 
http://blog.gmosx.com
http://cull.gr
http://www.joy.gr
http://nitroproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20070131/907817d1/attachment.html 


More information about the Nitro-general mailing list