Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Turbolinks doesn't recognize form re-submission [POST] and navigates instead [GET]. #251

azeezahmed opened this Issue Mar 20, 2017 · 6 comments


None yet
7 participants
Copy link

azeezahmed commented Mar 20, 2017

Steps to Reproduce

  1. scaffold a test_app with name: string as a required field.
  2. Run migrations.
  3. start rails server. link to test app
  4. have the form to generate errors ( name can't be blank )
  5. click refresh button (F5).

Expected Behaviour

The user should see browser confirm dialog box for form resubmission as below ( POST ).

Actual Behaviour

The page navigates to /users ( users#index, sends GET request).

Removing //= require turbolinks from asset pipeline restores the expected behaviour.
Did not find this issue being reported, please feel free to tag if it's a duplicate of an existing issue.


ruby 2.3.3p222
Rails 5.0.2
Turbolinks 5.0.1


This comment has been minimized.

Copy link

focused commented Apr 20, 2017

similar to #229 and #60


This comment has been minimized.

Copy link

kstratis commented Aug 15, 2017

I confirm the issue.
After an invalid submission I always land on /users/. To make matters worse, after I hit refresh, I get 404 unless I "protect" the index page somehow.

This should definitely be fixed.


This comment has been minimized.

Copy link

1Mark commented Dec 29, 2017

Is there any progress with this?


This comment has been minimized.

Copy link

ezr-ondrej commented Aug 8, 2018


1 similar comment

This comment has been minimized.

Copy link

paulodeleo commented Sep 19, 2018



This comment has been minimized.

Copy link

domchristie commented Sep 21, 2018

Closing as duplicate of #60. I have added some more detail explaining the complexity in #60 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.