pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2016-09-30	Update ruby-http-cookie to 1.0.3.	taca	2	-7/+7
	## 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.
2015-11-04	Add SHA512 digests for distfiles for www category	agc	1	-1/+2
	Problems found locating distfiles: Package haskell-cgi: missing distfile haskell-cgi-20001206.tar.gz Package nginx: missing distfile array-var-nginx-module-0.04.tar.gz Package nginx: missing distfile encrypted-session-nginx-module-0.04.tar.gz Package nginx: missing distfile headers-more-nginx-module-0.261.tar.gz Package nginx: missing distfile nginx_http_push_module-0.692.tar.gz Package nginx: missing distfile set-misc-nginx-module-0.29.tar.gz Package nginx-devel: missing distfile echo-nginx-module-0.58.tar.gz Package nginx-devel: missing distfile form-input-nginx-module-0.11.tar.gz Package nginx-devel: missing distfile lua-nginx-module-0.9.16.tar.gz Package nginx-devel: missing distfile nginx_http_push_module-0.692.tar.gz Package nginx-devel: missing distfile set-misc-nginx-module-0.29.tar.gz Package php-owncloud: missing distfile owncloud-8.2.0.tar.bz2 Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2013-09-15	Add ruby-http-cookie package version 1.0.2.	taca	4	-0/+83
	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.