- 04 11月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 28 8月, 2012 2 次提交
-
-
由 Piotr Sarnacki 提交于
AV::Template::Types is a small abstraction to allow to specify template types that can be used in ActionView. When Action Pack is loaded it's replaced with Mime::Type.
-
由 Piotr Sarnacki 提交于
default_formats array is used by LookupContext in order to allow rendering templates when :formats option is not passed. Previously it was always set to Mime::SET, which created dependency on Action Pack. In order to remove this dependency, Mime::SET is used only if ActionController is loaded.
-
- 22 8月, 2012 1 次提交
-
-
由 José Valim 提交于
The new option allows any Ruby namespace to be registered and set up for eager load. We are effectively exposing the structure existing in Rails since v3.0 for all developers in order to make their applications thread-safe and CoW friendly.
-
- 17 8月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
Since we removed the ActiveModel dependenxy from ActionPack at 166dbaa7 we don't need to require it anymore. Closes #7370
-
- 03 8月, 2012 2 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
This is a private place to put those AS features that are used by every component. Nowadays we cherry-pick individual files wherever they are used, but that it is not worth the effort for stuff that is going to be loaded for sure sooner or later, like blank?, autoload, concern, etc.
-
- 30 7月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 12 5月, 2012 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 18 3月, 2012 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 01 1月, 2012 1 次提交
-
-
由 Andrew Nesbitt 提交于
-
- 24 12月, 2011 2 次提交
-
-
由 José Valim 提交于
-
由 Sergey Nartimov 提交于
set AD::IntegrationTest.app in railtie initializer
-
- 16 12月, 2011 2 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
- 02 12月, 2011 2 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
- 22 10月, 2011 1 次提交
-
-
由 Brian Durand 提交于
-
- 20 10月, 2011 1 次提交
-
-
由 David Heinemeier Hansson 提交于
-
- 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 2 次提交
-
-
由 José Valim 提交于
-
由 Joshua Peek 提交于
-