- 07 4月, 2011 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 23 2月, 2011 1 次提交
-
-
由 Prem Sichanugrist 提交于
Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
- 20 12月, 2010 1 次提交
-
-
由 John Firebaugh 提交于
Based on the implementation on the 2-3-stable branch, patches by Hongli Lai <hongli@phusion.nl>, and helpful suggestions from José Valim. Hongli Lai's patches included locking around the request cycle; this is now handled by Rack::Lock (https://github.com/rack/rack/issues/issue/87/). [#2873] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 26 9月, 2010 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
This removes all deprecated classes in ActionController related to Routing, Abstract Request/Response and Integration/IntegrationTest. All tests and docs were changed to ActionDispatch instead of ActionController.
-
- 28 7月, 2010 1 次提交
-
-
由 wycats 提交于
Add a header that tells Internet Explorer (all versions) to use the best available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin. This guarantees that the best available standards support will be used on the client.
-
- 21 7月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
- 20 7月, 2010 1 次提交
-
-
由 Bryan Helmkamp 提交于
Signed-off-by: Nwycats <wycats@gmail.com>
-
- 03 6月, 2010 1 次提交
-
-
由 wycats 提交于
If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
-
- 30 5月, 2010 1 次提交
-
-
由 wycats 提交于
If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
-
- 04 3月, 2010 2 次提交
-
-
由 Carlhuda 提交于
* ActionController::Base.ip_spoofing_check deprecated => config.action_dispatch.ip_spoofing_check * ActionController::Base.trusted_proxies deprecated => config.action_dispatch.trusted_proxies
-
由 Carl Lerche 提交于
-
- 01 2月, 2010 1 次提交
-
-
由 Mikel Lindsaar 提交于
-
- 30 1月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 21 1月, 2010 3 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Prem Sichanugrist 提交于
Move filter_parameter_logging logic out of the controller and create ActionDispatch::ParametersFilter to handle parameter filteration instead. This will make filteration not depending on controller anymore. Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 17 1月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 Joshua Peek 提交于
-
- 16 1月, 2010 3 次提交
-
-
由 José Valim 提交于
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
- 05 1月, 2010 1 次提交
-
-
由 Joshua Peek 提交于
-
- 31 12月, 2009 2 次提交
-
-
由 Jeremy Kemper 提交于
Removes load path change from commit bb153f42.
-
由 Carl Lerche 提交于
-
- 29 12月, 2009 1 次提交
-
-
由 Carl Lerche 提交于
-
- 27 12月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 23 12月, 2009 3 次提交
-
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
由 Joshua Peek 提交于
-
- 21 12月, 2009 2 次提交
-
-
由 Joshua Peek 提交于
-
由 Yehuda Katz 提交于
-
- 17 12月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
adding any to the load path more than once.
-
- 13 12月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 03 12月, 2009 1 次提交
-
-
由 Carlhuda 提交于
* A new module (ActiveSupport::Autoload) is provide that extends autoloading with new behavior. * All autoloads in modules that have extended ActiveSupport::Autoload will be eagerly required in threadsafe environments * Autoloads can optionally leave off the path if the path is the same as full_constant_name.underscore * It is possible to specify that a group of autoloads live under an additional path. For instance, all of ActionDispatch's middlewares are ActionDispatch::MiddlewareName, but they live under "action_dispatch/middlewares/middleware_name" * It is possible to specify that a group of autoloads are all found at the same path. For instance, a number of exceptions might all be declared there. * One consequence of this is that testing-related constants are not autoloaded. To get the testing helpers for a given component, require "component_name/test_case". For instance, "action_controller/test_case". * test_help.rb, which is automatically required by a Rails application's test helper, requires the test_case.rb for all active components, so this change will not be disruptive in existing or new applications.
-
- 20 10月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 06 10月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 27 9月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 26 9月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-
- 24 9月, 2009 1 次提交
-
-
由 Joshua Peek 提交于
-