search for: session_expires

Hi everyone, I''m new to Rails and web development. I just bought up the Agile book and I''ve got a question about the :session_expires option. In the book, page 317, it says the :session_expires "option should probably not be used." Does anyone know why? The book doesn''t explain or give any indication as to why. In an application I''m working on I have a need to keep some information for a very lo...

from the Agile Book, i see i can set the absolute session expiry time via: ActionController::CGIRequest::DEFAULT_SESSION_OPTIONS[:session_expires] however, I don''t see anything about what the actual default setting is when a session is created. also, is there a way to set the expiration to happen when the browser is closed? in PHP, this can be accomplished using session.cookie_lifetime 0 in php.ini can this be accomplished in...

...this has no effect-- I can still log in multiple times with the admin account. For [2], I''m assuming this would be done by setting a time limit on the session. Researching ActionController::Base#process_cgi (which apparently is just an alias for Ruby''s CGI::Session) turns up the :session_expires option which seems to be what I''m looking for. However, I see the following in the AWD book, pg.306: ":session_expires The absolute time of the expiry of this session. Like :new_session, this option should probably not be used under Rails." Hmmm. Any suggestions...

There''s got to be a simple answer to this... def logout reset_session flash[:notice] = "Logged out" redirect_to :action => ''index'' end The flash never shows up, and doesn''t seem to be in the new session. --Al Evans -- Posted via http://www.ruby-forum.com/.

According to the Rails book, the session object has an attribute called :session_expires, but they don''t encourage its use. Currently I handle session expiry by using a cron job to delete session files that have not been modified in the last X minutes (it is a design/security requirement for this project that sessions expire after a finite period of inactivity). However,...

I''ve been looking around for how to store the session ID in a cookie. The "Agile Web Development with Rails" books seems to indicate that this is done by default with Rails. But I don''t see a cookie being set in my browser. (yeah, they''re enabled) I poked through the RForum code to find something referencing "cookies" but nothing came up. Does

...ion in my environment.rb file but I keep getting a syntax error on WeBRICK startup. I''m trying both of the ways listed in http://wiki.rubyonrails.org/rails/pages/HowtoChangeSessionOptions. FYI I''m new to rails so this is probably easy. 1) ActionController::Base.session_options[:session_expires] = Time.local(2008,"jan")) or 2) config.action_controller.session :session_expires => Time.local(2008,"jan")) but either way I keep getting the following syntax error: => Booting WEBrick... c:/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `gem_original_...

How do I keep the Rails session from expiring when the browser exits? I would ideally like the user to be logged for a few days (e.g. 2 weeks). Do I use the Rails "session" or "cookies"? Also, my understanding is that session[:session_expires] doesn''t work. Thanks. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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-...

How do I display, in breakpointer for example, session.session_key or session.session_expires ?? The only one that works is session.session_id for some reason. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060517/d99e0837/attachment-0001.html

======================================================================= "Try to be like the turtle - at ease in your own shell." Bill Copeland ======================================================================= Release Announcements --------------------- This is the last bug-fix release of the Samba 4.0 release series. There will be security releases only starting

======================================================================= "Try to be like the turtle - at ease in your own shell." Bill Copeland ======================================================================= Release Announcements --------------------- This is the last bug-fix release of the Samba 4.0 release series. There will be security releases only starting

Upgrading a Rails app from 2.2 to 2.3.2 (via 2.3.0). Got things working in the browser, but script/console seems messed up in both 2.3.0 and 2.3.2: $ script/console Loading development environment (Rails 2.3.2) /Library/Ruby/Gems/1.8/gems/rails-2.3.2/lib/initializer.rb:56:in `env'':NameError: uninitialized constant Module::ActiveSupport

I am looking into creating a website similar to a chat program. I know when the user logs in. However, the user can log out any of the following ways: Logout link - This one is easy to handle User closer browser window User hits the back button User loses his/her internt connection. Is there a way within rails to handle the latter three user actions? Thanks! -- Posted via

Hai,, I am totally new to Ajax. I am trying to use ajax in my project. Its working fine, I am getting problem while session time expires. If session expires means i am redirecting to login page.Onclick i am calling on ajax function. It will goto controller and it will check the session if session expires then it has to goto login page. On ajax call i am updating the div. If session

...ion FileUtils.rm "public/#{file.filename}" } emrec.destroy reset_session end I need to execute the same functionality when their session times out and I''m having a real problem understanding how to go about it. If I understand what I''ve read, the :session_expires option, which I''d hoped to use to control their timeout, works with cookie-based, client-side session management, not server-side. Is that right? Is there a way to do server-side session mgmt. in a case like this? TIA, Bill --~--~---------~--~----~------------~-------~--~----~ You rece...

...to get it to work. I have tried the following 2 methods but neither seem to work. When i check the expiry time in firefox it always says "end of session". What is the proper way to handle this so the session cookie "_session_id" doesnt expire for a year? I tried session[:session_expires] = 1.year.from_now and cookies[:_session_id] = { :value => session.session_id, :expires => Time.now+31536000, :domain => ".domain.com" } I get the following in the log, but viewing the cookie in firefox doesnt reflect this... Cookie set: _session_id=8813731b821e4b2e9210428d42a7...

Release Announcements --------------------- This is the fourth release candidate of Samba 4.2. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.2 will be the next version of the Samba suite. IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3

Release Announcements --------------------- This is the fourth release candidate of Samba 4.2. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.2 will be the next version of the Samba suite. IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3

Release Announcements --------------------- This is the fifth release candidate of Samba 4.2. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.2 will be the next version of the Samba suite. IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3

Release Announcements --------------------- This is the fifth release candidate of Samba 4.2. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.2 will be the next version of the Samba suite. IMPORTANT NOTE ABOUT THE SUPPORT END OF SAMBA 3