From 0894d73c7552a4c7d576b7d3692c6a18faadd273 Mon Sep 17 00:00:00 2001 From: Hendy Tanata Date: Fri, 15 Jul 2011 21:56:03 +0800 Subject: Fix wildcard route code examples. Should be "match" instead of "map". --- railties/guides/source/routing.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'railties/guides/source') diff --git a/railties/guides/source/routing.textile b/railties/guides/source/routing.textile index 06b3579720..57e390f385 100644 --- a/railties/guides/source/routing.textile +++ b/railties/guides/source/routing.textile @@ -560,13 +560,13 @@ would match +zoo/woo/foo/bar/baz+ with +params[:a]+ equals +"zoo/woo"+, and +par NOTE: Starting from Rails 3.1, wildcard routes will always match the optional format segment by default. For example if you have this route: -map '*pages' => 'pages#show' +match '*pages' => '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: -map '*pages' => 'pages#show', :format => false +match '*pages' => 'pages#show', :format => false h4. Redirection -- cgit v1.2.3