- 21 5月, 2012 1 次提交
-
-
由 Andrew White 提交于
Passing path parameters with invalid encoding is likely to trigger errors further on like `ArgumentError (invalid byte sequence in UTF-8)`. This will result in a 500 error whereas the better error to return is a 400 error which allows exception notification libraries to filter it out if they wish. Closes #4450
-
- 15 5月, 2012 1 次提交
-
-
由 Kornelius Kalnbach 提交于
-
- 11 5月, 2012 2 次提交
-
-
由 Andrew White 提交于
-
由 Andrew White 提交于
-
- 09 5月, 2012 2 次提交
-
-
由 Andrew White 提交于
-
由 Nikita Beloglazov 提交于
-
- 07 5月, 2012 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 05 5月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
This fixes the following scenario: resources :contacts do post 'new', action: 'new', on: :collection, as: :new end Where the /new path is not generated because it's considered a canonical action, part of the normal resource actions: new_contacts POST /contacts(.:format) contacts#new Fixes #2999
-
- 03 5月, 2012 1 次提交
-
-
由 Andrew White 提交于
A callable object passed as a constraint for a route may access the request parameters as part of its check. This causes the combined parameters hash to be cached in the environment hash. If the constraint fails then any subsequent access of the request parameters will be against that stale hash. To fix this we delete the cache after every call to `matches?`. This may have a negative performance impact if the contraint wraps a large number of routes as the parameters hash is built by merging GET, POST and path parameters. Fixes #2510.
-
- 30 4月, 2012 2 次提交
-
-
由 Andrew White 提交于
-
由 Andrew White 提交于
-
- 25 4月, 2012 1 次提交
-
-
由 Jose and Yehuda 提交于
In the current router DSL, using the +match+ DSL method will match all verbs for the path to the specified endpoint. In the vast majority of cases, people are currently using +match+ when they actually mean +get+. This introduces security implications. This commit disallows calling +match+ without an HTTP verb constraint by default. To explicitly match all verbs, this commit also adds a :via => :all option to +match+. Closes #5964
-
- 26 3月, 2012 1 次提交
-
-
由 Jamie Macey 提交于
By default, resources routes are created with :resource/:id. A model defining to_param can make prettier urls by using something more readable than an integer ID, but since the route picks it up as :id you wind up with awkward User.find_by_username(params[:id]) calls. By overriding the key to be used in @request.params you can be more obvious in your intent.
-
- 25 2月, 2012 2 次提交
-
-
由 kennyj 提交于
-
由 Xavier Noria 提交于
uses PATCH for the forms of persisted records, and routes PATCH and PUT to the update action of resources
-
- 22 2月, 2012 1 次提交
-
-
由 kennyj 提交于
-
- 16 2月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 11 2月, 2012 2 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
- 10 2月, 2012 1 次提交
-
-
由 kennyj 提交于
-
- 06 2月, 2012 2 次提交
-
-
由 Jeremy Kemper 提交于
Too painful to lose the compact shorthand form! This reverts commit e848c525. Conflicts: actionpack/lib/action_dispatch/routing/mapper.rb
-
由 kennyj 提交于
Fix url_for method's behavior when it is called with :controller option which starts with "/" from multiple nested controller. Closes #3864
-
- 28 1月, 2012 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
The commit 4c321c6d removes the path_params variable assignment, actually the entire line is not used at all.
-
由 kennyj 提交于
-
- 26 1月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
Test for unicode path support
-
- 24 1月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 14 1月, 2012 1 次提交
-
-
由 Sam Pohlenz 提交于
-
- 06 1月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
- 22 12月, 2011 1 次提交
-
-
由 Aaron Patterson 提交于
-
- 16 12月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 13 12月, 2011 1 次提交
-
-
由 José Valim 提交于
-
- 19 11月, 2011 3 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 14 10月, 2011 2 次提交
-
-
由 Jeremy Kemper 提交于
-
由 Jeremy Kemper 提交于
-
- 11 10月, 2011 1 次提交
-
-
由 Diego Carrion 提交于
-
- 22 9月, 2011 1 次提交
-
-
由 Pawel Pierzchala 提交于
-
- 12 8月, 2011 1 次提交
-
-
由 Andrew Kaspick 提交于
when calling url_for with a hash, additional (likely unwanted) values (such as :host) would be returned in the hash... calling #dup on the hash prevents this
-
- 26 7月, 2011 1 次提交
-
-
由 Dave Rogers 提交于
addresses issue #1907 - any routes that follow a route with a constraints block are inheriting the previous route's constraints.
-