He's not talking about a framework, he's talking about web application firewalls that only support the default verbs. It's quite common and has nothing to do with which framework you use.
Re:Some REST best practices
by politician on Monday November 17, 2014 @04:34PM
(#8620773)
Thanks for clearing that up, yes, as I've said, you should not use custom verbs if you have to interop with firewalls or proxy caches that perform DPI unless you've tested them.
Re:Some REST best practices
by mistermumble on Monday November 17, 2014 @06:13PM
(#8621360)
Problem is that you may test the system now and it all works fine. But the day after you deploy, somebody named Murphy adds or updates a proxy somewhere in your topology that breaks things. Or your organization gets a new customer or partner with a differently configured network.
Re:Some REST best practices
by politician on Monday November 17, 2014 @08:34PM
(#8621942)
That's an argument for never doing anything.
Re:Some REST best practices
by toomuchtodo on Monday November 17, 2014 @10:20PM
(#8622208)
Its an argument for being conservative in your design philosophy.
A framework that doesn't support extensible verbs in 2014 is bound to have more problems than just a failure to implement one RFC correctly.