aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/routing.md
diff options
context:
space:
mode:
authorVijay Dev <vijaydev.cse@gmail.com>2012-12-08 23:11:37 +0530
committerVijay Dev <vijaydev.cse@gmail.com>2012-12-08 23:11:37 +0530
commit0a33fcd68bb2c56b8c2eba066f343484a44fa588 (patch)
treed54d667ff16f99274fdec0edaf7df98bf8eba6ef /guides/source/routing.md
parent1233fc6de145932f3cd46c784ea78234cfa743b2 (diff)
parent729798068a54dbbe553c71f0283cb6ad74c2e77c (diff)
downloadrails-0a33fcd68bb2c56b8c2eba066f343484a44fa588.tar.gz
rails-0a33fcd68bb2c56b8c2eba066f343484a44fa588.tar.bz2
rails-0a33fcd68bb2c56b8c2eba066f343484a44fa588.zip
Merge branch 'master' of github.com:lifo/docrails
Diffstat (limited to 'guides/source/routing.md')
-rw-r--r--guides/source/routing.md16
1 files changed, 5 insertions, 11 deletions
diff --git a/guides/source/routing.md b/guides/source/routing.md
index 714c0b609e..241a7cfec6 100644
--- a/guides/source/routing.md
+++ b/guides/source/routing.md
@@ -5,11 +5,11 @@ This guide covers the user-facing features of Rails routing.
After reading this guide, you will know:
-* Understand the code in `routes.rb`.
-* Construct your own routes, using either the preferred resourceful style or the `match` method.
-* Identify what parameters to expect an action to receive.
-* Automatically create paths and URLs using route helpers.
-* Use advanced techniques such as constraints and Rack endpoints.
+* How to interpret the code in `routes.rb`.
+* How to construct your own routes, using either the preferred resourceful style or the `match` method.
+* What parameters to expect an action to receive.
+* How to automatically create paths and URLs using route helpers.
+* Advanced techniques such as constraints and Rack endpoints.
--------------------------------------------------------------------------------
@@ -733,12 +733,6 @@ get '*a/foo/*b', to: 'test#index'
would match `zoo/woo/foo/bar/baz` with `params[:a]` equals `'zoo/woo'`, and `params[:b]` equals `'bar/baz'`.
-NOTE: Starting from Rails 3.1, wildcard segments will always match the optional format segment by default. For example if you have this route:
-
-```ruby
-get '*pages', to: 'pages#show'
-```
-
NOTE: By requesting `'/foo/bar.json'`, your `params[:pages]` will be equals to `'foo/bar'` with the request format of JSON. If you want the old 3.0.x behavior back, you could supply `format: false` like this:
```ruby