Tapestry-routing (http://tynamo.org/tapestry-routing+guide) explicitly
doesn't allow Index pages but lets you specify context-less routes instead
and gives 404 for anything else. I've always thought that's the way it
should work by default.

Kalle

On Mon, Jan 5, 2015 at 12:27 PM, Chris Poulsen <mailingl...@nesluop.dk>
wrote:

> yeah, examine the eventcontext and return an error/error page or whatever,
> if it does not contain what you expect.
>
> On Mon, Jan 5, 2015 at 8:28 PM, George Christman <gchrist...@cardaddy.com>
> wrote:
>
> > So are you saying throw an exception if the home page onActivate
> > contains any type of activation context?
> >
> > On Mon, Jan 5, 2015 at 11:53 AM, Chris Poulsen <mailingl...@nesluop.dk>
> > wrote:
> > > A strict onActivate in the index page can handle this
> > >
> > > On Mon, Jan 5, 2015 at 4:10 PM, George Christman <
> > gchrist...@cardaddy.com>
> > > wrote:
> > >
> > >> Hi guys, I'm wondering if Tapestry has a configuration setting some
> > >> where to prevent the framework from redirecting non existing pages to
> > >> the Index. This creates an SEO nightmare when pages are removed from
> > >> the app, but still exist in the search engines index. They end up
> > >> seeing the index page as having two URL's with duplicate meta tags
> > >> which crushes your page rank. A desired behavior would be to redirect
> > >> them to a page not found. If anybody knows of an easy way to do to
> > >> this, please let me know. Thanks.
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > >> For additional commands, e-mail: users-h...@tapestry.apache.org
> > >>
> > >>
> >
> >
> >
> > --
> > George Christman
> > CEO
> > www.CarDaddy.com
> > P.O. Box 735
> > Johnstown, New York
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> > For additional commands, e-mail: users-h...@tapestry.apache.org
> >
> >
>

Reply via email to