For a particular set of actions, I have a before and an after filter. When the before filter returns false, however, the after filter still executes (which I can tell because an error is being thrown from it.) I know the before filter successfully returns false, because the logs show that the chain was halted. What could be causing the after filter to run despite the halting of the chain in the before filter? (This is on Rails 1.2.3, and none of the plug-ins I''m using appear to modify the filter functionality of ActionController in any way.) Thanks in advance for any insight you can provide. Ian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 20 Nov 2007, at 00:01, Ian Lesperance wrote:> > For a particular set of actions, I have a before and an after filter. > When the before filter returns false, however, the after filter still > executes (which I can tell because an error is being thrown from it.) > I know the before filter successfully returns false, because the logs > show that the chain was halted. > > What could be causing the after filter to run despite the halting of > the chain in the before filter? > > (This is on Rails 1.2.3, and none of the plug-ins I''m using appear to > modify the filter functionality of ActionController in any way.) > > Thanks in advance for any insight you can provide.This bit me a while back. IIRC, this is just the way things are. Fred --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
A-ha. Looks like this was fixed for Rails 1.2.4 with Revision 7177. Ian On Nov 19, 8:08 pm, Frederick Cheung <frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 20 Nov 2007, at 00:01, Ian Lesperance wrote: > > > > > For a particular set of actions, I have a before and anafterfilter. > > When the beforefilterreturns false, however, theafterfilterstill > > executes (which I can tell because an error is being thrown from it.) > > I know the beforefiltersuccessfully returns false, because the logs > > show that the chain was halted. > > > What could be causing theafterfilterto run despite the halting of > > the chain in the beforefilter? > > > (This is on Rails 1.2.3, and none of the plug-ins I''m using appear to > > modify thefilterfunctionality of ActionController in any way.) > > > Thanks in advance for any insight you can provide. > > This bit me a while back. IIRC, this is just the way things are. > > Fred--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Reasonably Related Threads
- Slow RAID Check/high %iowait during check after updgrade from CentOS 6.5 -> CentOS 7.2
- Slow RAID Check/high %iowait during check after updgrade from CentOS 6.5 -> CentOS 7.2
- Slow RAID Check/high %iowait during check after updgrade from CentOS 6.5 -> CentOS 7.2
- Restarting BackgrounDRb Means Restarting Mongrel?
- Slow RAID Check/high %iowait during check after updgrade from CentOS 6.5 -> CentOS 7.2