On Fri, Nov 12, 2010 at 2:15 AM, R00ted R. <[email protected]> wrote: > Marnen Laibow-Koser wrote in post #960749: >> R00ted R. wrote in post #960744: >>> I have Rails 2.3.2 and I want to disable session support for one >>> controller action, so that means that I don't want to save session >>> variables to database when I'm accessing url. For example '/my_action' >>> url. I have tried to implement this using session :off, :only => >>> :my_action but this doesn't work. >>> >>> The message I recieve is: DEPRECATION WARNING: Disabling sessions for a >>> single controller has been deprecated. Sessions are now lazy loaded. So >>> if you don't access them, consider them off. You can still modify the >>> session cookie options with request.session_options.. >> >> Did you read the message? Did you notice the second sentence? Does >> that suggest anything? Have you tried that approach? >> >> Best, >> -- >> Marnen Laibow-Koser >> http://www.marnen.org >> [email protected] > > > Yes, I have read this sentence. I'm not accessing any session variable > or setting them but anyway system creates a session record, wich I don't > need. Maybe I don't understand the idea. I need any suggestions..
The session is not created until you check to see if the session is created. Do not check the session. > -- > 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 [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. > > -- 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 [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.
