Up to [cvs.NetBSD.org] / pkgsrc / www / ruby-http-cookie
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
www/ruby-http-cookie: update to 1.1.6 1.1.5 (2026-04-19) * Fix NameError: uninitialized constant HTTP::Cookie::MAX_COOKIES_TOTAL when http/cookie_jar is required without http/cookie, as done by the http gem. (#62) 1.1.6 (2026-04-20) * Use autoload to avoid "circular require" warnings between http/cookie and http/cookie_jar. (#65)
www/ruby-http-cookie: update to 1.1.4 1.1.1 (2026-04-06) * Fix thread-unsafe runtime requires. (#43 by @brasic, #57) * Replace require 'cgi' with require 'cgi/escape' to suppress Ruby 4.0 warning. (#56 by @dominion525) * Do not define MozillaStore on JRuby; leave the constant undefined instead. * Relax sqlite3 development dependency to >= 1.3. 1.1.2 (2026-04-06) * Stop requiring sqlite3 at load time by changing MozillaStore::Database from inheritance to composition. 1.1.3 (2026-04-06) * Restore compatibility with Ruby 2.6. 1.1.4 (2026-04-07) * Fix require "http/cookie_jar" raising NameError: uninitialized constant HTTP. (#61)
www/ruby-http-cookie: update to 1.1.0 1.1.0 (2025-09-26) * Implement Cookie#to_h. (#55) @luke-hill @flavorjones * Reduce gem size by excluding test files (#54) @yuri-zubov
www/ruby-http-cookie: update to 1.0.8 1.0.8 (2024-12-05) * Cookie#expires= accepts DateTime objects. (#52) @luke-hill @flavorjones New Contributors * @luke-hill made their first contribution in #52
www/ruby-http-cookie: update to 1.0.7 1.0.7 (2024-06-06) * Explicitly require "cgi" to avoid NameError in some applications. (#50 by @flavorjones)
www/ruby-http-cookie: update to 1.0.6 1.0.6 (2024-06-01) * Fix error formatting bug in HTTP::CookieJar::AbstractStore (#42 by @andrelaszlo) * Allow non-RFC 3986-compliant URLs (#45 by @c960657) * Add coverage for Ruby 3.2 and 3.3 (#46 by @flavorjones) * Quash ruby 3.4 warnings (#47 by @flavorjones)
www/ruby-http-cookie: update to 1.0.5 1.0.5 (2022-05-25) * Silence SQLite3 warnings
www/ruby-http-cookie: update to 1.0.4 1.0.4 (2021-06-07) No change log, please refer <https://github.com/sparklemotion/http-cookie/compare/v1.0.3...v1.0.4> in detail.
Pullup ticket #5112 - requested by taca
www/ruby-http-cookie: security fix
Revisions pulled up:
- www/ruby-http-cookie/Makefile 1.2
- www/ruby-http-cookie/distinfo 1.3
---
Module Name: pkgsrc
Committed By: taca
Date: Fri Sep 30 15:36:59 UTC 2016
Modified Files:
pkgsrc/www/ruby-http-cookie: Makefile distinfo
Log Message:
Update ruby-http-cookie to 1.0.3.
## 1.0.3 (2016-09-30)
- Treat comma as normal character in HTTP::Cookie.cookie_value_to_hash
instead of key-value pair separator. This should fix the problem
described in CVE-2016-7401.
Update ruby-http-cookie to 1.0.3. ## 1.0.3 (2016-09-30) - Treat comma as normal character in HTTP::Cookie.cookie_value_to_hash instead of key-value pair separator. This should fix the problem described in CVE-2016-7401.
Add ruby-http-cookie package version 1.0.2. HTTP::Cookie is a ruby library to handle HTTP cookies in a way both compliant with RFCs and compatible with today's major browsers. It was originally a part of the [Mechanize](https://github.com/sparklemotion/mechanize) library, separated as an independent library in the hope of serving as a common component that is reusable from any HTTP related piece of software. The following is an incomplete list of its features: * Its behavior is highly compatible with that of today's major web browsers. * It is based on and conforms to RFC 6265 (the latest standard for the HTTP cookie mechanism) to a high extent, with real world conventions deeply in mind. * It takes eTLD (effective TLD, also known as "Public Suffix") into account just as major browsers do, to reject cookies with an eTLD domain like "org", "co.jp", or "appspot.com". This feature is brought to you by the domain_name gem. * The number of cookies and the size are properly capped so that a cookie store does not get flooded. * It supports the legacy Netscape cookies.txt format for serialization, maximizing the interoperability with other implementations. * It supports the cookies.sqlite format adopted by Mozilla Firefox for backend store database which can be shared among multiple program instances. * It is relatively easy to add a new serialization format or a backend store because of its modular API.