wycats 25215d7285 Fix several known web encoding issues: ... * Specify accept-charset on all forms. All recent browsers, as well as IE5+, will use the encoding specified for form parameters * Unfortunately, IE5+ will not look at accept-charset unless at least one character in the form's values is not in the page's charset. Since the user can override the default charset (which Rails sets to UTF-8), we provide a hidden input containing a unicode character, forcing IE to look at the accept-charset. * Now that the vast majority of web input is UTF-8, we set the inbound parameters to UTF-8. This will eliminate many cases of incompatible encodings between ASCII-8BIT and UTF-8. * You can safely ignore params[:_snowman_] TODO: * Validate inbound text to confirm it is UTF-8 * Combine the whole_form implementations in form_helper_test and form_tag_helper_test		2010-06-27 21:13:55 -07:00
..
json_params_parsing_test.rb	Disable ShowExceptions during integration tests	2010-01-19 09:06:21 -06:00
multipart_params_parsing_test.rb	Upgrade to Rack 1.2.1	2010-06-27 17:55:23 -07:00
query_string_parsing_test.rb	Ruby 1.9: resolve constant lookup issues	2009-11-04 15:41:50 -08:00
url_encoded_params_parsing_test.rb	Fix several known web encoding issues:	2010-06-27 21:13:55 -07:00
xml_params_parsing_test.rb	Ruby 1.9: fix invalid rack response in test	2010-05-15 11:25:56 -07:00