Skip to content
A Mechanize extension that allows cookies to be saved in more advanced stores than serialized filesystem files
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Build Status

mechanize-cookie_store is an extension to mechanize gem that allows you to persist the mechanize agent cookie set in a smarter way than serialized or plain files in the server's system. One of its biggest benefits is allowing you to share your cookies across multiple server instances.


Add this line to your application's Gemfile:

gem 'mechanize-cookie_store'

And then execute:

$ bundle

Or install it yourself as:

$ gem install mechanize-cookie_store


For Rails applications you can create config/initializers/mechanize-cookie_store.rb and provide the necessary configuration params to access your desired persistance method.

If you're not using Rails, you just need to make sure to run the same configuration code before using Mechanize.

Please see below the available built-in stores and their specific configurations:

Currently, the only supported store is Redis.

For Redis

Mechanize::CookieStore.configure do |config|
  config.connection_params = {
    url: "your-redis-url",
    namespace: "your-redis-namespace" # optional
  • url must have a valid redis server url
  • namespace parameter is optional, default namespace is mechanize_cookies


After configuring it, usage looks pretty similar to the way you would use mechanize without this gem.

Instantiate a mechanize session and use it:

agent =


Then save orload your cookie_jar the same way you would do it without mechanize-cookie_store. # to persist cookies to storage

agent.cookie_jar.load # to load back back into the agent from storage

Or use if you want to load specific cookie set you can pass to load the options domain, path and name like this:

agent.cookie_jar.load(domain: "", path: "/mypath", name: "myCookie")

Please note that these options correpond to the fields of the HTTP::Cookie class, an inherited dependency from Mechanize.


This gem depends on:


  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 a new Pull Request

To run the test suite, make sure you have Redis server running in localhost:6379. Then just run bundle exec rake


The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the Mechanize::CookieStore project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.

You can’t perform that action at this time.