In production mode (Debug = 0), Cake just displays the generic 404 error view I believe. From there you could work which part of the url is wrong if you wanted, or just display the same view for either type (or other) of error.
On Jul 24, 6:11 pm, mark_story <[email protected]> wrote: > Well if the request doesn't match any user land routes, cake tries to > use its default routes. If those generate errors, that's what > happens. > > -Mark > > On Jul 24, 10:23 am, DragonFlyEye <[email protected]> wrote: > > > OK, I'm trying to figure this out and getting wacky results as I test: > > I'm playing with custom-built routes in the following format: > > > /:town-name/:action/:id > > > The route works fine for correct URLs, but I'm confused as to what > > CakePHP does with URLs which don't conform to the regex included in > > the third argument to the Router::connect() method. Here is my code: > > > Router::connect( > > '/:town-name/:action/:id', > > array('controller' => 'potholes'), > > array( > > 'town-name' => '[a-z/-]+', > > 'id' => '[a-z/-]+')); > > > If I put in an erroneous URL like /roch3ster/view/this-post, I get the > > error "Roch3sterController could not be found." If I put one in that > > messes up the third parameter, /rochester/view/bo3ogers, I get > > "RochesterController could not be found." > > > It may be that some of the other routing I'm doing is messing up the > > show. But can anyone tell me what the expected behavior aught to be? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
