#5813: [PATCH] HTTP code mapping should be moved to a specific protected method
--------------------------------------------+-------------------------------
    Reporter:  rafaelbandeira3              |         Owner:         
        Type:  Enhancement                  |        Status:  new    
    Priority:  Medium                       |     Milestone:  1.2.x.x
   Component:  Controller                   |       Version:  RC3    
    Severity:  Minor                        |    Resolution:         
    Keywords:  controller redirect headers  |   Php_version:  n/a    
Cake_version:                               |  
--------------------------------------------+-------------------------------
Comment (by grigri):

 Whoa. Sorry, I didn't mean to sound sarcastic. I ''do'' think this is a
 good idea, I just gave an off-beat example.

 I ran into this on a project a while ago (can't remember exactly what, but
 it had nothing to do with HTCPCP), but thought the case was too specific
 to warrant a ticket/change to the core. Now that I see it wasn't an
 isolated case, perhaps it does.

 (Apologies for adding another not-very-useful comment ticket to trac)

-- 
Ticket URL: <https://trac.cakephp.org/ticket/5813#comment:3>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tickets-cakephp?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to