After some further testing, this seems a little bazaar. The following code will run both the Subdomain and Authenticated constraints when accessing a resource:
scope :constraints => Subdomain.new do resources :something, :constraints => Authenticated.new end However, with the root route specified (your scenario), it only runs the constraint attached directly to the root route. Not sure if this is a bug, or the intended behavior of the root route. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-talk/-/xa6YU1jiyToJ. 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/rubyonrails-talk?hl=en.
