#6261: Auth deny method doesn't respect methods name case
-------------------------------+--------------------------------------------
    Reporter:  biscazziere     |         Owner:           
        Type:  Enhancement     |        Status:  new      
    Priority:  Medium          |     Milestone:  1.2.x.x  
   Component:  Auth            |       Version:  1.2 Final
    Severity:  Normal          |    Resolution:           
    Keywords:  auth deny case  |   Php_version:  PHP 5    
Cake_version:                  |  
-------------------------------+--------------------------------------------
Changes (by gwoo):

  * type:  Bug => Enhancement

Comment:

 Relevant code is
 
https://trac.cakephp.org/browser/branches/1.2.x.x/cake/libs/controller/components/auth.php#L296

 So according to this if you are accessing and action with camelcase you
 must specified the allowed/denied action in camelcase. However, this will
 also cause issues because methods are case insensitive in php4.

 My suggestion is to always use lower case and underscore actions. I will
 move to an enhancement for 1.3 so that all actions and checks will be
 converted to lowercase.

-- 
Ticket URL: <https://trac.cakephp.org/ticket/6261#comment:1>
CakePHP : The Rapid Development Framework for PHP <https://trac.cakephp.org/>
Cake is a rapid development framework for PHP which uses commonly known design 
patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. 
Our primary goal is to provide a structured framework that enables PHP users at 
all levels to rapidly develop robust web applications, without any loss to 
flexibility.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tickets cakephp" group.
To post to this group, send email to tickets-cakephp@googlegroups.com
To unsubscribe from this group, send email to 
tickets-cakephp+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to