1. 25 5月, 2011 1 次提交
  2. 13 4月, 2011 1 次提交
  3. 09 2月, 2011 1 次提交
  4. 04 10月, 2010 1 次提交
  5. 29 9月, 2010 3 次提交
  6. 19 9月, 2010 1 次提交
  7. 05 9月, 2010 1 次提交
  8. 17 8月, 2010 1 次提交
  9. 14 8月, 2010 2 次提交
  10. 20 6月, 2010 1 次提交
  11. 15 6月, 2010 1 次提交
  12. 17 5月, 2010 3 次提交
    • W
      Revert "Moved encoding work in progress to a feature branch." · 80b60671
      wycats 提交于
      This reverts commit ade756fe.
      80b60671
    • J
      Moved encoding work in progress to a feature branch. · ade756fe
      Jeremy Kemper 提交于
      This reverts commits af0d1a88 and 64d109e3.
      ade756fe
    • W
      Significantly improved internal encoding heuristics and support. · 64d109e3
      wycats 提交于
      * Default Encoding.default_internal to UTF-8
      * Eliminated the use of file-wide magic comments to coerce code evaluated inside the file
      * Read templates as BINARY, use default_external or template-wide magic comments
        inside the Template to set the initial encoding
        * This means that template handlers in Ruby 1.9 will receive Strings encoded
          in default_internal (UTF-8 by default)
      * Create a better Exception for encoding issues, and use it when the template
        source has bytes that are not compatible with the specified encoding
      * Allow template handlers to opt-into handling BINARY. If they do so, they
        need to do some of their own manual encoding work
      * Added a "Configuration Gotchas" section to the intro Rails Guide instructing
        users to use UTF-8 for everything
      * Use config.encoding= in Ruby 1.8, and raise if a value that is an invalid
        $KCODE value is used
      
      Also:
      * Fixed a few tests that were assert() rather than assert_equal() and
        were caught by Minitest requiring a String for the message
      * Fixed a test where an assert_select was misformed, also caught by
        Minitest being more restrictive
      * Fixed a test where a Rack response was returning a String rather
        than an Enumerable
      64d109e3
  13. 16 5月, 2010 2 次提交
  14. 19 3月, 2010 2 次提交
  15. 18 3月, 2010 1 次提交
  16. 14 3月, 2010 1 次提交
  17. 09 3月, 2010 1 次提交
  18. 24 2月, 2010 1 次提交
  19. 17 2月, 2010 2 次提交
  20. 27 12月, 2009 1 次提交
    • J
      Remove ActionView inline logging to ActiveSupport::Notifications and create... · 75ba102a
      José Valim 提交于
      Remove ActionView inline logging to ActiveSupport::Notifications and create ActionController::Base#log_event, so everything can be logged within one listener. Also expose log_process_action as a hook for different modules to include their own information during the action processing. This allow ActiveRecord to hook and any other ORM. Finally, this commit changes 'Processing' and 'Rendering' in logs to 'Processed' and 'Rendered' because at the point it's logged, everying already happened.
      75ba102a
  21. 23 12月, 2009 1 次提交
  22. 09 12月, 2009 1 次提交
  23. 02 12月, 2009 1 次提交
  24. 05 11月, 2009 1 次提交
  25. 27 10月, 2009 1 次提交
  26. 08 10月, 2009 1 次提交
    • M
      Switch to on-by-default XSS escaping for rails. · 94159359
      Michael Koziarski 提交于
        This consists of:
      
        * String#html_safe! a method to mark a string as 'safe'
        * ActionView::SafeBuffer a string subclass which escapes anything unsafe which is concatenated to it
        * Calls to String#html_safe! throughout the rails helpers
        * a 'raw' helper which lets you concatenate trusted HTML from non-safety-aware sources (e.g. presantized strings in the DB)
        * New ERB implementation based on erubis which uses a SafeBuffer instead of a String
      
      Hat tip to Django for the inspiration.
      94159359
  27. 17 8月, 2009 1 次提交
  28. 16 8月, 2009 1 次提交
  29. 09 8月, 2009 1 次提交
  30. 07 8月, 2009 3 次提交