redirect_to
- 1.0.0
- 1.1.6
- 1.2.6
- 2.0.3
- 2.1.0
- 2.2.1
- 2.3.8
- 3.0.0 (0)
- 3.0.9 (6)
- 3.1.0 (12)
- 3.2.1 (4)
- 3.2.8 (21)
- 3.2.13 (0)
- 4.0.2 (-4)
- 4.1.8 (0)
- 4.2.1 (3)
- 4.2.7 (0)
- 4.2.9 (0)
- 5.0.0.1 (-20)
- 5.1.7 (12)
- 5.2.3 (0)
- 6.0.0 (0)
- 6.1.3.1 (0)
- 6.1.7.7 (0)
- 7.0.0 (38)
- 7.1.3.2 (0)
- 7.1.3.4 (0)
- What's this?
redirect_to(options = {}, response_status = {})
public
Redirects the browser to the target specified in options. This parameter can be any one of:
-
Hash - The URL will be generated by calling url_for with the options.
-
Record - The URL will be generated by calling url_for with the options, which will reference a named URL for that record.
-
String starting with protocol:// (like http://) or a protocol relative reference (like //) - Is passed straight through as the target for redirection.
-
String not containing a protocol - The current protocol and host is prepended to the string.
-
Proc - A block that will be executed in the controller’s context. Should return any option accepted by redirect_to.
Examples:
redirect_to action: "show", id: 5 redirect_to post redirect_to "http://www.rubyonrails.org" redirect_to "/images/screenshot.jpg" redirect_to articles_url redirect_to proc { edit_post_url(@post) }
The redirection happens as a “302 Found” header unless otherwise specified using the :status option:
redirect_to post_url(@post), status: :found redirect_to action: 'atom', status: :moved_permanently redirect_to post_url(@post), status: 301 redirect_to action: 'atom', status: 302
The status code can either be a standard HTTP Status code as an integer, or a symbol representing the downcased, underscored and symbolized description. Note that the status code must be a 3xx HTTP code, or redirection will not occur.
If you are using XHR requests other than GET or POST and redirecting after the request then some browsers will follow the redirect using the original request method. This may lead to undesirable behavior such as a double DELETE. To work around this you can return a 303 See Other status code which will be followed using a GET request.
redirect_to posts_url, status: :see_other redirect_to action: 'index', status: 303
It is also possible to assign a flash message as part of the redirection. There are two special accessors for the commonly used flash names alert and notice as well as a general purpose flash bucket.
redirect_to post_url(@post), alert: "Watch it, mister!" redirect_to post_url(@post), status: :found, notice: "Pay attention to the road" redirect_to post_url(@post), status: 301, flash: { updated_post_id: @post.id } redirect_to({ action: 'atom' }, alert: "Something serious happened")
Redirect to subdomain
If you’re looking to redirect to a subdomain you can do things like this:
redirect_to users_url(1, params: {a: :b}, subdomain: 'bob')