rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Cookie store: use OpenSSL::HMAC instead of basic hash. Introduce :secret ↵	Jeremy Kemper	2007-03-03	1	-21/+49
\| \| \| \| \| \|	block and :digest option. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6296 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
*	Cookie store: test that >4K raises CookieOverflow and that unverifiable ↵	Jeremy Kemper	2007-03-03	1	-13/+43
\| \| \| \| \| \|	cookies are automatically deleted. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6294 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
*	Cookie session store: empty and unchanged sessions don't write a cookie.	Jeremy Kemper	2007-02-25	1	-1/+15
\| \| \| \|	git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6226 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
*	CGI escape the session cookie.	Jeremy Kemper	2007-02-22	1	-2/+2
\| \| \| \|	git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6200 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
*	Introduce a cookie-based session store as the Rails default. Sessions ↵	Jeremy Kemper	2007-02-21	1	-0/+137
	typically contain at most a user_id and flash message; both fit within the 4K cookie size limit. A secure hash is included with the cookie to ensure data integrity (a user cannot alter his user_id without knowing the secret key included in the hash). If you have more than 4K of session data or don't want your data to be visible to the user, pick another session store. Cookie-based sessions are dramatically faster than the alternatives. git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@6184 5ecf4fe2-1ee6-0310-87b1-e25e094e27de