1. 16 8月, 2016 1 次提交
  2. 14 8月, 2016 1 次提交
  3. 07 8月, 2016 2 次提交
  4. 17 2月, 2016 1 次提交
    • J
      Remove unused Journey code · 84826b4e
      Jon Moss 提交于
      - `VERSION` shouldn't be there anymore since Journey is technically part
      of Action Dispatch now (and thus Action Pack, and follows the normal
      Rails versioning scheme)
      - `backwards.rb` was only in the file tree because early in the history
        or Journey (back in 2011!), it was moved from under the Rack namespace, to its own
      namespace, Journey! This file is no longer required, and is assigning
      constants that are no longer needed.
      84826b4e
  5. 15 8月, 2015 2 次提交
  6. 14 8月, 2015 1 次提交
    • A
      remove Strexp · 947ebe9a
      Aaron Patterson 提交于
      This was a useless object.  We can just directly construct a
      Path::Pattern object without a Strexp object.
      947ebe9a
  7. 21 3月, 2015 1 次提交
    • H
      Respect routing precedence for HEAD requests · 34a52c6b
      Harry Marr 提交于
      Fixes the issue described in #18764 - prevents Rack middleware from
      swallowing up HEAD requests that should have been matched by a
      higher-precedence `get` route, but still allows Rack middleware to
      respond to HEAD requests.
      34a52c6b
  8. 27 2月, 2015 1 次提交
  9. 26 2月, 2015 1 次提交
    • G
      Partition routes during setup. · 89edfbd3
      Guo Xiang Tan 提交于
      Partitioning of all the routes is currently being done during the
      first request. Since there is no need to clear the cache for
      `partitioned_routes` when adding a new route. We can move the
      partitioning of the routes during setup time.
      89edfbd3
  10. 09 2月, 2015 1 次提交
    • T
      Explicitly ignored wildcard verbs from head_routes · b9c63b0a
      Terence Sun 提交于
      In match_head_routes, deleted the routes in which request.request_method was empty (matches all HTTP verbs) when responding to a HEAD request. This prevents catch-all routes (such as Racks) from intercepting the HEAD request.
      
      Fixes #18698
      b9c63b0a
  11. 29 11月, 2014 1 次提交
  12. 21 8月, 2014 1 次提交
    • G
      Avoid duplicating routes for HEAD requests. · d3eb92d9
      Guo Xiang Tan 提交于
      Follow up to rails#15321
      
      Instead of duplicating the routes, we will first match the HEAD request to
      HEAD routes. If no match is found, we will then map the HEAD request to
      GET routes.
      d3eb92d9
  13. 20 6月, 2014 1 次提交
    • V
      Replace x.sort_by!.select! with x.select!.sort_by! · 8ee785a1
      Viktar Basharymau 提交于
      The latter has the same speed as the former in the worst case
      and faster in general, because it is always better to sort less items.
      
      Unfortunately, `routes.select!{...}.sort_by!{...}` is not possible here
      because `select!` returns `nil`, so select! and sort! must be done
      in two steps.
      8ee785a1
  14. 14 6月, 2014 1 次提交
  15. 26 5月, 2014 2 次提交
  16. 25 5月, 2014 1 次提交
  17. 24 5月, 2014 9 次提交
  18. 23 5月, 2014 2 次提交
  19. 22 5月, 2014 3 次提交
  20. 02 4月, 2014 1 次提交
  21. 16 1月, 2014 1 次提交
  22. 21 6月, 2013 1 次提交
    • P
      Don't remove trailing slash from PATH_INFO for mounted apps · 50311f13
      Piotr Sarnacki 提交于
      Previously when app was mounted as following:
      
          class Foo
            def call(env)
              [200, {}, [env['PATH_INFO']]]
            end
          end
      
          RackMountRailsBug::Application.routes.draw do
            mount RackTest.new => "/foo"
          end
      
      trailing slash was removed from PATH_INFO. For example requesting
      
          GET /foo/bar/
      
      on routes defined above would result in a response containing "/foo/bar"
      instead of "/foo/bar/".
      
      This commit fixes the issue.
      
      (closes #3215)
      50311f13
  23. 16 4月, 2013 1 次提交
  24. 16 1月, 2013 1 次提交
    • A
      Add support for other types of routing constraints · 90d2802b
      Andrew White 提交于
      This now allows the use of arrays like this:
      
        get '/foo/:action', to: 'foo', constraints: { subdomain: %w[www admin] }
      
      or constraints where the request method returns an Fixnum like this:
      
        get '/foo', to: 'foo#index', constraints: { port: 8080 }
      
      Note that this only applies to constraints on the request - path
      constraints still need to be specified as Regexps as the various
      constraints are compiled into a single Regexp.
      90d2802b
  25. 21 12月, 2012 1 次提交
  26. 20 12月, 2012 1 次提交