erm no

the important thing is that what we do is set the 404 header

that way the filter chain knows its a 404 and can handle it properly

as opposed to us happily streaming our own error page with a 200

-igor


On 3/14/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:

exactly

-igor


On 3/14/07, Jean-Baptiste Quenot <[EMAIL PROTECTED]> wrote:
>
> * Al Maw:
>
> > Err, if you  use a filter then you fall  through and do whatever
> > the container does. Please don't break it for the filter case.
>
> So you say it's not a  good idea to throw a PageNotFoundException,
> rather  ensure that  isWicketRequest()  returns false  to let  the
> request flow to the next filter in the chain?
> --
>      Jean-Baptiste Quenot
> aka  John Banana   Qwerty
> http://caraldi.com/jbq/
>


Reply via email to