Redirect uses status code 302 which does not work with Turbo

[mrkcor]

Redirect uses status code 302 which does not work with Turbo

[ryenski]

I have been using the edge version which includes #223 without problems. This changes the response to 422 Unprocessable Entity, which is compatible with Turbo.

gem 'responders', github: 'heartcombo/responders'

[mdavidn]

This appears to fix the problem:

class ApplicationController < ActionController::Base
  # ...

  def redirect_to(url_options = {}, response_options = {})
    response_options[:status] ||= :see_other unless request.get?
    super url_options, response_options
  end
end

[carlosantoniodasilva]

Can you point to the docs where it mentions 303 only? I was under the impression that any redirect would do.

We do have an unreleased change on master about the 422 on errors: #223, I ran into a problem while testing it out and haven't been able to circle back on it again, but maybe that would help with what you're looking for?

[mrkcor]

It is mentioned here: https://turbo.hotwire.dev/handbook/drive#redirecting-after-a-form-submission

422 responses work fine for me :)

[seyerian]

The issue remains that Turbo expects a 303 rather than redirect_to's 302. In particular, given:

class PostsController < ApplicationController
  ...
  def destroy
    @post.destroy
    respond_with(@post)
  end
end

On a successful DELETE:

1. there are no model errors
2. Responders redirects with 302 Location posts_path
3. Turbo follows that as DELETE posts_path, which results in a routing error

Turbo's subsequent request is a DELETE (the original method) presumably because that is how fetch operates in conformance to the HTTP spec. See hotwired/turbo#84 (comment)

mrkcor's snippet in the OP fixes this issue between Responders and Turbo.

[mdavidn]

This looks like a bug in Rails itself, in ActionController::Redirecting#redirect_to. 303 is the correct response code for a non-GET request if the client should use GET with the new location. This bug persists because all browsers (and curl -L) do not follow the spec and will change a POST into a GET after any redirect.