You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
docuseal/vendor/bundle/ruby/4.0.0/gems/rack-session-2.1.2
Wabo d9b86d464c
Restore fork-specific features lost during upstream sync:
3 weeks ago
..
lib/rack Restore fork-specific features lost during upstream sync: 3 weeks ago
license.md Restore fork-specific features lost during upstream sync: 3 weeks ago
readme.md Restore fork-specific features lost during upstream sync: 3 weeks ago
releases.md Restore fork-specific features lost during upstream sync: 3 weeks ago
security.md Restore fork-specific features lost during upstream sync: 3 weeks ago

readme.md

Rack::Session

Session management implementation for Rack.

Development Status

Usage

In your config.ru:

# config.ru

require 'rack/session'
use Rack::Session::Cookie,
  :domain => 'mywebsite.com',
  :path => '/',
  :expire_after => 3600*24,
  :secret => '**unique secret key**'

Usage follows the standard outlined by rack.session, i.e.:

class MyApp
  def call(env)
    session = env['rack.session']

    # Set some state:
    session[:key] = "value"
  end
end

Compatibility

rack-session code used to be part of Rack, but it was extracted in Rack v3 to this gem. The v1 release of this gem is compatible with Rack v2, and the v2 release of this gem is compatible with Rack v3+. That means you can add gem "rack-session" to your application and it will be compatible with all versions of Rack.

Contributing

We welcome contributions to this project.

  1. Fork it.
  2. Create your feature branch (git checkout -b my-new-feature).
  3. Commit your changes (git commit -am 'Add some feature').
  4. Push to the branch (git push origin my-new-feature).
  5. Create new Pull Request.