I have routes_onerror( (*/*, '/init/default/error') )
the controller just brings up a search based on the requested_uri. -Thadeus On Mon, Mar 15, 2010 at 1:10 PM, Magnitus <[email protected]> wrote: > On Mar 14, 9:58 pm, Graham Dumpleton <[email protected]> > wrote: >> You can potentially also use any error page as a tell tale fingerprint >> if defaults are used as different frameworks are going to each have >> their own. > > Not only that, I find it very revelative that it states whether the > app is wrong, the controller is wrong or the function is wrong. > > Its good for the developper to know this, but not for the user. > > Frankly, the less the user knows about the type of server "error" he > caused, the happier I will be. > > I was considering re-routing all mispelled urls to a default error > page. > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
