aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application/middleware_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Calls to the application constant have been refactored to usewangjohn2013-06-101-2/+2
| | | | | Rails.application when drawing routes and creating other configurations on the application.
* Testing CheckPending middlewareArun Agrawal2013-06-081-0/+8
|
* Bring config.allow_concurrency backJosé Valim2013-03-031-0/+6
| | | | | Since the Rack::Lock still exists in development, let's provide a way to disable it explicitly.
* Remove BestStandardsSupport middlewareGuillermo Iguaran2013-01-291-2/+1
|
* Don't use action_controller.perform_caching to enable rack-rack.Rafael Mendonça França2012-10-181-4/+1
| | | | | Setting the action_dispatch.rack_cache options to true or a hash should be the way to enable it.
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-141-4/+4
|
* config.action_dispatch.rack_cache should set explicitly to enable Rack::CacheGuillermo Iguaran2012-10-041-1/+10
|
* Remove unused require.kennyj2012-08-291-2/+0
|
* Remove allow_concurrency as a flagJosé Valim2012-08-211-2/+2
| | | | | | | | | | | | | | | | The flag was mainly used to add a Rack::Lock middleware to the stack, but the only scenario the lock is desired is in development. If you are deploying on a not-threaded server, the Rack::Lock does not provide any benefit since you don't have concurrent accesses. On the other hand, if you are on a threaded server, you don't want the lock, since it defeats the purpose of using a threaded server. If there is someone out there, running on a thread server and does want a lock, it can be added to your environment as easy as: `use Rack::Lock`
* Remove ActionDispatch::Head middleware in favor of Rack::HeadSantiago Pastorino2012-07-231-1/+1
| | | | Closes #7110 there's more work to do on rack-cache issue 69
* Freeze the middleware stack after it's builtJeremy Kemper2012-04-201-0/+7
| | | | | | So apps that accidentally add middlewares later aren't unwittingly dumping them in a black hole. Closes #5911
* Rack::SSL -> ActionDispatch::SSLRafael Mendonça França2012-03-171-3/+3
|
* Remove --http.José Valim2012-03-141-30/+0
|
* Add test to ensure setting config.generators.http_only actually disables the ↵Carlos Antonio da Silva2012-03-141-1/+1
| | | | | | generator options [Carlos Antonio da Silva & Santiago Pastorino]
* Remove IdentityMapCarlos Antonio da Silva2012-03-131-7/+0
|
* Change api_only to http_onlyCarlos Antonio da Silva2012-03-101-2/+1
| | | | [Carlos Antonio da Silva & Santiago Pastorino]
* Add config.middleware.api_only!Carlos Antonio da Silva and Santiago Pastorino2012-03-051-0/+30
|
* Handle files from ActionDispatch::Static with Rack::Sendfile (fixes #5225)Piotr Sarnacki2012-03-031-1/+1
| | | | | | | | This makes rails behave properly when you serve static assets and you have X-Sendfile headers enabled. Nevertheless in most cases you should not rely on that and serve static assets with a webserver like Apache or Nginx (as you already have it in place anyway if you use X-Sendfile)
* Deprecate RAILS_CACHE constant.kennyj2012-01-181-2/+2
|
* convert railties to use AS::TestCaseAaron Patterson2012-01-051-1/+1
|
* Add ORIGINAL_FULLPATH to envPiotr Sarnacki2011-12-211-1/+10
| | | | | | | | | | | This behaves similarly to REQUEST_URI, but we need to implement it on our own because REQUEST_URI is not reliable. Note that since PATH_INFO does not contain information about trailing question mark, this is not 100% accurate, for example `/foo?` will result in `/foo` in ORIGINAL_FULLPATH
* Split ShowExceptions responsibilities in two middlewares.José Valim2011-12-011-1/+3
|
* Allow rescue responses to be configured through a railtie.José Valim2011-12-011-21/+1
|
* Adding ActionDispatch::RequestId in middleware testArun Agrawal2011-10-201-0/+1
|
* Make the Rack::SSL middleware configurableJustin Leitgeb2011-09-261-0/+8
|
* Check that Rack::Sendfile is not included unless ↵Santiago Pastorino2011-08-131-0/+8
| | | | config.action_dispatch.x_sendfile_header is set
* Solve the RAILS_ENV problem in the railties tests in a more generic wayJon Leighton2011-06-061-1/+5
|
* Move content length to the server, this brings the same behavior as in rack 1.2.José Valim2011-05-231-7/+6
|
* Temporarily ship with ContentLength middleware.José Valim2011-05-201-3/+3
|
* Use Rack::ContentLength.José Valim2011-05-191-5/+6
|
* Fix tests to reflect IdentityMap no longer defaultDavid Lee2011-05-101-1/+1
| | | | Broke in 0e1dcae1857db4f6721561caff38d8be748d0b40
* Logs should show overridden method; Issue 426David Lee2011-05-071-2/+2
|
* s/with/when/Xavier Noria2011-03-271-1/+1
|
* Add `config.force_ssl` configuration which will load `Rack::SSL` middleware ↵Prem Sichanugrist2011-03-271-0/+6
| | | | | | | | if set to true This will allow user to be able to force all requests to be under HTTPS protocol. This commit was a request from DHH. Special thanks to Josh Peek as well for making `Rack::SSL`.
* Always use ActionDispatch::ShowExceptions middleware [#6462 state:resolved]Prem Sichanugrist2011-02-251-2/+2
| | | | This will make sure the application will raise `ActionController::RoutingError` in case "X-Cascade: pass" header was set, usually when there's no route match.
* We really don't care about IM middleware order, the important is that it ↵Emilio Tagua2011-02-181-1/+1
| | | | gets included.
* Merge remote branch 'rails/master' into identity_mapEmilio Tagua2010-12-201-0/+7
|\ | | | | | | | | | | | | | | Conflicts: activerecord/lib/active_record/associations/association_proxy.rb activerecord/lib/active_record/autosave_association.rb activerecord/lib/active_record/base.rb activerecord/lib/active_record/persistence.rb
| * Introduce ActionDispatch::ReloaderJohn Firebaugh2010-12-201-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | 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: José Valim <jose.valim@gmail.com>
* | Don't load IdentityMap middleware if not enabled. Simplify middleware.Emilio Tagua2010-11-191-0/+5
| |
* | Use IdentityMap middleware to flush map on each request.Emilio Tagua2010-11-191-0/+2
|/
* Move ETag and ConditionalGet logic from AD::Response to the middleware stack.José Valim2010-10-031-21/+43
|
* Fix a routing test. Reorganize middleware tests.José Valim2010-10-021-91/+0
|
* Only add Rack::Cache to the middleware stack if ↵Sparky2010-09-151-4/+31
| | | | config.action_controller.perform_caching is set.
* First pass at Rack::Cachewycats2010-09-131-4/+5
|
* Revert "Just add connection management middleware if running in a concurrent ↵Jeremy Kemper2010-08-201-0/+1
| | | | | | environment." This reverts commit 6b29dc876fe185881d46731c3ae170478a3828fe.
* Fix middleware testwycats2010-07-271-1/+2
|
* application generation: --skip-testunit and --skip-activerecord renamed to ↵Xavier Noria2010-07-251-1/+1
| | | | | | | | --skip-test-unit and --skip-active-record respectively Reason is their proper spellings are "Test::Unit" and "Active Record". Option names and descriptions have been revised, as well as some method names and minor details here and there.
* Just add connection management middleware if running in a concurrent ↵José Valim2010-07-121-1/+0
| | | | environment.
* adding middleware test for RAILS_CACHENeeraj Singh2010-06-241-0/+11
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Ensure show exceptions middleware properly filters backtrace before logging.José Valim2010-06-091-0/+20
|