redirect_to
redirect_to(options = {}, response_options = {})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 posts_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](www.iana.org/assignments/http-status-codes) 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")
Statements after `redirect_to` in our controller get executed, so `redirect_to` doesn’t stop the execution of the function. To terminate the execution of the function immediately after the `redirect_to`, use return.
redirect_to post_url(@post) and return
### Open Redirect protection
By default, Rails protects against redirecting to external hosts for your app’s safety, so called open redirects. Note: this was a new default in Rails 7.0, after upgrading opt-in by uncommenting the line with `raise_on_open_redirects` in `config/initializers/new_framework_defaults_7_0.rb`
Here #redirect_to automatically validates the potentially-unsafe URL:
redirect_to params[:redirect_url]
Raises UnsafeRedirectError in the case of an unsafe redirect.
To allow any external redirects pass `allow_other_host: true`, though using a user-provided param in that case is unsafe.
redirect_to "https://rubyonrails.org", allow_other_host: true
See #url_from for more information on what an internal and safe URL is, or how to fall back to an alternate redirect URL in the unsafe case.
1Note
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')