The Mechanize library is used for automating interaction with websites. Mechanize automatically stores and sends cookies, follows redirects, can follow links, and submit forms. Form fields can be populated and submitted. Mechanize also keeps track of the sites that you have visited as a history.
Graceful session key rotation for the signed cookie store in Rails 3.
A simple utility to detect incompatible user agents for `SameSite=None` cookie attribute
Rack middleware to log in from a "remember me" Devise cookie.
Adds Rails like cookie support to grape api
Generates Rails code for an authentication system and persistent cookie management.
This library is a Ruby reference implementation for dealing with consent strings in the IAB EU's GDPR Transparency and Consent Framework. It should be used by anyone who receives or sends consent information like vendors that receive consent data from a partner, or consent management platforms that need to encode/decode the global cookie. The IAB specification for the consent string format is available on the IAB Github (section 'Vendor Consent Cookie Format'). This library supports the version v1.1 of the specification. It can encode and decode consent strings with version bit 1.
Cookie's Javascript/CSS/View Layout for Alert generator
Rails extension to help with cookies in a system with sub-domains
This plugin helps you to serialize your records into very short strings for storing in cookies.
The Mechanize library is used for automating interaction with websites. Mechanize automatically stores and sends cookies, follows redirects, can follow links, and submit forms. Form fields can be populated and submitted. Mechanize also keeps track of the sites that you have visited as a history.
A simple integration bootstrap, Add some cookies.
A Rails 3.1 & 3.2 version of Encrypted Cookie Store by FooBarWidget
Declarative API for specifying features, switchable in declaration, database and cookies.
Chinese fortune cookies
This Gem makes cookies if cookies were files derived from erb templates.
A gem that eats cookies
Disable cookies for RackTest
a better cookie session store for rack.
A middleware the prevents access to a rack app without the proper cookie.
Use this gem as an extra layer of protection if your system has any HTTP accelerators in front of it, like varnish.
A simple way to add cookie disclaimer.
Helpers and partials to display cookie contents, even for encrypted cookies. Not meant for production
A terminal based Cookie Clicker style game.
Used to encode and decode cookies used in a single sign on implementation within the same domain
Download "liked" music of Douban FM by cookie
Lightweight web framework inspired by Sinatra
Raamen is a Rack and SQLite based MVC web framework. It contains modules to provide basic and necessary features of web app components as well as helpful Rack middleware, cookie manipulation, and CLI to make the development process faster and easier.
Secure JWT authentication for Ruby on Rails that uses http only cookies.
RoR before_filter to detect mobile browsers
Hashed cookie-based session store for Rack
Generate cookie with viewer id in same domain services.
A library for working with Set-Cookie data in Ruby
A bunch of rack middlewares to enforce secure cookies and add HSTS (Strict Transport Security) and HPKP (Public Key Pinning) headers to your Rack application.
Lookout-Rack Lookout-Rack provides easy interaction with Rack¹ from Lookout². It provides you with a session connected to your Rack application through which you can make requests, check responses, follow redirects and set, inspect, and clear cookies. ¹ See http://rack.rubyforge.org/ ² See http://disu.se/software/lookout/ § Installation Install Lookout-Rack with % gem install lookout-rack § Usage Include the following code in your ‹Rakefile› (provided that you’re using Lookout-Rake¹): require 'lookout-rack-3.0' Lookout::Rake::Tasks::Test.new do |t| t.requires << 'lookout-rack-3.0' end ¹ See http://disu.se/software/lookout-rake/ Then set up a ‹fixtures/config.ru› file that Lookout-Rack will use for loading your Rack app. load 'path/to/app.rb' use Rack::Lint run Path::To::App This file, if it exists, will be loaded during the first call to #session. If it doesn’t exist, ‹config.ru› will be used instead. You can now test your app: Expectations do expect 200 do session.get('/').response.status end end The #session method returns an object that lets you #get, #post, #put, and #delete resources from the Rack app. You call these method with a URI¹ that you want to access/modify together with any parameters that you want to pass and any Rack environment that you want to use (which isn’t very common). For example, let’s get ‹/pizzas/› with olives on them: expect 200 do session.get('/pizzas/', 'olives' => '1').response.status end ¹ Abbreviation for Uniform Resource Identifier The #response method on #session returns a mock Rack response object that can be queried for results. Similarly, there’s a #request method that lets you inspect the request that was made. Lookout-Rack also deals with cookies. Assuming that ‹/cookies/set/› will set any cookies that we pass it and that ‹/cookies/show/› will simply do nothing relevant, the following expectation will pass: expect 'value' => '1' do session. get('/cookies/set/', 'value' => '1'). get('/cookies/show/').request.cookies end Sometimes you may want to set cookies yourself before making a request. You then use the #cookie method, which takes a String of ‹KEY=VALUE› pairs separated by newlines, commas, and/or semicolons and sets those cookies in the session: expect 'value' => '1', 'other' => '2' do session. cookie("value=1\n\nother=2"). get('/cookies/show/').request.cookies end You may also want to clear all cookies in your session using #clear: expect({}) do session. get('/cookies/set', 'value' => '1'). clear. get('/cookies/show').request.cookies end Finally, to test redirects, call the #redirect! method on the session object, assuming that ‹/redirected/› redirects to another location: expect result.redirect? do session.get('/redirected/').response end expect result.not.redirect? do session.get('/redirected/').redirect!.response end That’s basically all there’s to it. You can check the {API documentation}¹ for more information. ¹ See http://disu.se/software/lookout-rack/api/Lookout/Rack/ § Financing Currently, most of my time is spent at my day job and in my rather busy private life. Please motivate me to spend time on this piece of software by donating some of your money to this project. Yeah, I realize that requesting money to develop software is a bit, well, capitalistic of me. But please realize that I live in a capitalistic society and I need money to have other people give me the things that I need to continue living under the rules of said society. So, if you feel that this piece of software has helped you out enough to warrant a reward, please PayPal a donation to now@disu.se¹. Thanks! Your support won’t go unnoticed! ¹ Send a donation: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=now@disu.se&item_name=Lookout-Rack § Reporting Bugs Please report any bugs that you encounter to the {issue tracker}¹. ¹ See https://github.com/now/lookout-rack/issues § Authors Nikolai Weibull wrote the code, the tests, the documentation, and this README. § Licensing Lookout-Rack is free software: you may redistribute it and/or modify it under the terms of the {GNU Lesser General Public License, version 3}¹ or later², as published by the {Free Software Foundation}³. ¹ See http://disu.se/licenses/lgpl-3.0/ ² See http://gnu.org/licenses/ ³ See http://fsf.org/
A Ruby CLI gem that provides fortune cookie messages on your Terminal, based on the highlights on your Kindle device.
This simple middleware sets anything in the X-#{prefix}-Cookie header to Cookie, and in the response will copy anything in Set-Cookie to X-#{prefix}-Set-Cookie. This can be useful to enable session management where an HTML client is accessing your API, which doesn't fully support cookies. We have found this to be the case in some Smart TV web applications, and in mobile apps written using frameworks such as Cordova
Uses jStorage.js to allow browsers to store more information than is save to store in a Cookie
A Mechanize extension that allows cookies to be saved in more advanced stores than serialized filesystem files.
Rack middleware to support magic cookie on clients
BookingSync-Rack-P3p is rack middleware for inserting P3P headers into apps. This will allow your application to serve cookies to IE when in an iframe. It will also pull off the cookie on 304 responses, since IE does not like the cookie then.
Provides utilities to get user information from cookies within OpenStax Ruby apps.
nvd3.js is an attempt to build re-usable charts and chart components for d3.js without taking away the power that d3.js gives you. This is a very young collection of components, with the goal of keeping these components very customizeable, staying away from your standard cookie cutter solutions.
Removes specified cookies from HTTP request and / or response on user defined pages.
It helps admin to announce anything including parsed html in a form a notice.It consists two types of announcements: Session Based: Only for logged in users.(Application Layout), Cookie Based: For all users visiting the website.(Public Layout)
Like Rails' CookieStore for sessions, but uses JSON format rather than Marshaled ruby objects
Clean all the angle brackets from user input params and cookies! Based on https://github.com/madebymany/parameter_cleaner. Thanks to threedaymonk!
Reveals a URL given 1 or more URL redirects including handling the use of passive cookies which could affect the final URL revealed.
Track and identify users via cookie in order to run A/B tests.
trainmaster is a Rails engine that provides JWT-based session management platform for API development. This plugin is suitable for developing RESTful APIs that do not require an enterprise identity service. There are no cookies or non-unique IDs involved in this project.