1. 04 1月, 2015 1 次提交
  2. 02 1月, 2015 1 次提交
  3. 17 12月, 2014 1 次提交
  4. 23 11月, 2014 1 次提交
  5. 19 11月, 2014 1 次提交
  6. 18 11月, 2014 1 次提交
  7. 10 11月, 2014 1 次提交
    • G
      Pass the route name explicitly · aa6637d1
      Godfrey Chan 提交于
      Follow up to 212057b9. Since that commit, we need to pass the `route_name`
      explicitly. This is one of the left-over cases that was not handled in that
      commit, which was causing `use_route` to be ignored in functional tests.
      aa6637d1
  8. 30 9月, 2014 1 次提交
  9. 14 8月, 2014 1 次提交
  10. 07 8月, 2014 1 次提交
  11. 05 8月, 2014 1 次提交
  12. 25 7月, 2014 1 次提交
  13. 21 7月, 2014 1 次提交
  14. 16 7月, 2014 1 次提交
  15. 08 7月, 2014 1 次提交
  16. 03 7月, 2014 1 次提交
  17. 17 6月, 2014 5 次提交
  18. 13 6月, 2014 1 次提交
  19. 06 6月, 2014 1 次提交
  20. 23 5月, 2014 1 次提交
  21. 04 5月, 2014 2 次提交
  22. 27 4月, 2014 1 次提交
  23. 21 4月, 2014 4 次提交
  24. 20 4月, 2014 1 次提交
  25. 14 4月, 2014 1 次提交
  26. 25 3月, 2014 1 次提交
  27. 13 3月, 2014 2 次提交
    • A
      use the body proxy to freeze headers · 3df07d09
      Aaron Patterson 提交于
      avoid freezing the headers until the web server has actually read data
      from the body proxy.  Once the webserver has read data, then we should
      throw an error if someone tries to set a header
      3df07d09
    • A
      only write the jar if the response isn't committed · 77a09218
      Aaron Patterson 提交于
      when streaming responses, we need to make sure the cookie jar is written
      to the headers before returning up the stack. This commit introduces a
      new method on the response object that writes the cookie jar to the
      headers as the response is committed.  The middleware and test framework
      will not write the cookie headers if the response has already been
      committed.
      
      fixes #14352
      77a09218
  28. 01 3月, 2014 1 次提交
  29. 27 2月, 2014 1 次提交
    • T
      Fix controller test not resetting @_url_options · a351149e
      Tony Wooster 提交于
      Commit 4f2cd3e9 introduced a bug by reordering the call to
      `@controller.recycle!` above the call to `build_request_uri`. The
      impact of this was that the `@_url_options` cache ends up not being
      reset between building a request URI (occurring within the test
      controller) and the firing of the actual request.
      
      We encountered this bug because we had the following setup:
      
        class MinimumReproducibleController < ActionController::Base
          before_filter { @param = 'param' }
      
          def index
            render text: url_for(params)
          end
      
          def default_url_options
            { custom_opt: @param }
          end
        end
      
        def test_index
          get :index # builds url, then fires actual request
        end
      
      The first step in  `get :index` in the test suite would populate the
      @_url_options cache. The subsequent call to `url_for` inside of the
      controller action would then utilize the uncleared cache, thus never
      calling the now-updated default_url_options.
      
      This commit fixes this bug calling recycle! twice, and removes a call
      to set response_body, which should no longer be needed since we're
      recycling the request object explicitly.
      a351149e
  30. 27 1月, 2014 1 次提交
  31. 28 6月, 2013 1 次提交