So, this: why can :secret be a proc, and what is User.current_user

ActionDispatch::Session::CookieStore

So, this: why can :secret be a proc, and what is User.current_user

This cookie-based session store is the Rails default. Sessions typically contain at most a user_id and flash message; both fit within the 4K cookie size limit. Cookie-based sessions are dramatically faster than the alternatives. If you have more than 4K of session data or don’t want your data to be visible to the user, pick another session store. CookieOverflow is raised if you attempt to store more than 4K of data. A message digest is included with the cookie to ensure data integrity: a user cannot alter his user_id without knowing the secret key included in the hash. New apps are generated with a pregenerated secret in config/environment.rb. Set your own for old apps you’re upgrading. Session options: :secret : An application-wide key string or block returning a string called per generated digest. The block is called with the CGI::Session instance as an argument. It's im...

Full article: http://api.rubyonrails.org/classes/ActionDispatch/Session...

Tweets

@jcoglan » 05 Jan '13, 2pm
So, in light of that, are these docs wrong about the `Proc.new` thing, or is this a Rails bug? [link]
@tunixman » 05 Jan '13, 1pm
RT @jcoglan: So, this: [link] why can :secret be a proc, and what is User.current_user ?
@jcoglan » 05 Jan '13, 1pm
So, this: [link] why can :secret be a proc, and what is User.current_user ?
@jcoglan » 05 Jan '13, 1pm
@Espen_Antonsen I mean the setting in config/initializers. [link] says the secret can be a proc, am I missing something?
@Espen_Antonsen » 05 Jan '13, 1pm
@jcoglan [link] [link]