On Tuesday, April 2, 2013 9:41:59 PM UTC+7, [email protected] wrote: > > > To save people form themselves? To save the world? I really don't care. > > Bottom line: That blackholed request thing is a usability nightmare. You > merely have to reload the page >
Okay, That came out wrong. My question would be better phrased as: What makes you think that CakePHP turns on SecurityComponent by default? CakePHP does not turn on Security component by default. AFAIK, the core will _not_ enable SecurityComponent until explicitly asked to. Further, baked applications do not have have them by default. > > On Monday, April 1, 2013 6:41:44 AM UTC+1, rchavik wrote: >> >> >> >> On Thursday, March 28, 2013 4:57:38 PM UTC+7, [email protected] wrote: >>> >>> Security features like this that cause issues with basic flow, should be >>> OFF by default. CakePHP is it's own worst enemy for leaving it in. >>> >>> >> Why do you think CakePHP turns SecurityComponent on by default? >> > -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/cake-php?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
