Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6142295
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 23, 20262026-05-23T18:22:03+00:00 2026-05-23T18:22:03+00:00

So Devise has what seems to be two methods of accomplishing the same thing,

  • 0

So Devise has what seems to be two methods of accomplishing the same thing, firstly it seems the classic way of protecting a unauthorized user from accessing a controllers action would be something like this in my controller:

before_filter :authenticate_user!

But I’ve been seeing this done in the routes.rb more often now also like so:

authenticate :user do
  resources :reports
end

Which one should I be using?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-23T18:22:03+00:00Added an answer on May 23, 2026 at 6:22 pm

    That logic belongs to the controller, not routes. Routes are just what they are, routes. It’s not good to put some logic into them.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

If a user has many things and a thing has many stats, it seems
I recently upgraded from Devise 1.2 to 1.4.9 and everything seems to work except
Is there a way to determine what kind of data plan a device has
I'm using Rails 3 with Devise for user auth. Let's say I have a
I have an UIViewController that has two UIViews inside, whose layout (set in Interface
Hello I am trying to display two different html pages through the same UIViewController
My Rails 3 app has three customized controllers for my Devise + OmniAuth integration.
My solution in in c# has two projects. Each in their own seperate folder.
I'm using Devise for user authentication and basic authentication. Let's say I have defined
I have an Android Honeycomb application with two activities; the first one has a

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.