Merge branch 'cookbook_routing_nocontroller' of git://github.com/tacker/symfony-docs into tacker-cookbook_routing_nocontroller

weaverryan · weaverryan · commit e3615d710caa · 2012-07-14T18:54:12.000-05:00
Conflicts:
	cookbook/index.rst
	cookbook/map.rst.inc
diff --git a/cookbook/map.rst.inc b/cookbook/map.rst.inc
@@ -84,6 +84,7 @@
 
   * :doc:`/cookbook/routing/scheme`
   * :doc:`/cookbook/routing/slash_in_parameter`
+  * :doc:`/cookbook/routing/redirect_in_config`
 
 * **symfony1**
 
@@ -128,4 +129,4 @@
 * :doc:`/cookbook/workflow/index`
 
   * :doc:`/cookbook/workflow/new_project_git`
-  * :doc:`/cookbook/workflow/new_project_svn`
+  * :doc:`/cookbook/workflow/new_project_svn`
diff --git a/cookbook/routing/index.rst b/cookbook/routing/index.rst
@@ -6,3 +6,4 @@ Routing
 
     scheme
     slash_in_parameter
+    redirect_in_config
diff --git a/cookbook/routing/redirect_in_config.rst b/cookbook/routing/redirect_in_config.rst
@@ -0,0 +1,37 @@
+.. index::
+   single: Routing; Configure redirect to another route without a custom controller
+
+How to configure a redirect to another route without a custom controller
+========================================================================
+
+This guide explains how to configure a redirect from one route to another
+without using a custom controller.
+
+Let's assume that there is no useful default controller for the ``/`` path of
+your application and you want to redirect theses requests to ``/app``.
+
+Your configuration will look like this:
+
+.. code-block:: yaml
+
+    AppBundle:
+        resource: "@App/Controller/"
+        type:     annotation
+        prefix:   /app
+
+    root:
+        pattern: /
+        defaults:
+            _controller: FrameworkBundle:Redirect:urlRedirect
+            path: /app
+            permanent: true
+
+Your ``AppBundle`` is registered to handle all requests under ``/app``.
+
+We configure a route for the ``/`` path and let :class:`Symfony\\Bundle\\FrameworkBundle\\Controller\\RedirectController` handle it.
+This controller is builtin and offers two methods for redirecting request:
+
+   * ``redirect`` redirects to another *route*. You must provide the ``route`` parameter with the *name* of the route you want to redirect to.
+   * ``urlRedirect`` redirects to another *path*. You must provide the ``path`` parameter containing the path of the resource you want to redirect to.
+
+The ``permanent`` switch tells both methods to issue a 301 HTTP status code.

Original file line number	Diff line number	Diff line change
`@@ -6,3 +6,4 @@ Routing`
`6`	`6`
`7`	`7`	`scheme`
`8`	`8`	`slash_in_parameter`
	`9`	`+ redirect_in_config`