be the default behavior.
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/How-to-return-HTTP-404-for-in-exact-URL-requests-tp5715875p5715876.html
> Sent from the Tapestry - User
It sounds like you are fixing something that really should be handled by
tapestry. I agree that a 404 is much better than a 500 in these cases and I
think it should be the default behavior.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/How-to-return-HTTP-404-for-in
A topic that crops up time and time again is that of the elusive HTTP
404 in T5 apps.
When running a public website, for SEO reasons, it is desirable for
in-exact urls to return a HTTP 404 rather than returning a 'best fit'
page.For the same reasons, it is undesirable for malformed urls to
return
