Update is processed as HTML instead of JS about remotipart

[acesuares]

Yes, going back to

gem 'jquery-rails', '2.02' 

fixes this issue by going back to jQuery 1.7.2

[JangoSteve]

This should work now with jquery-rails 2.2.x in remotipart v1.0.3.

[shekibobo]

Was there anything in particular that solved this issue? I'm running Rails 3.2.13, jquery-rails 2.3.0, and remotipart 1.0.5, and I'm seeing this on my staging server. It seems to run just fine in my local development server. Despite everything from the headers, payload, whatever being the same on both environments, it works as js on my local, and html on my staging environment. When I don't handle html requests in my controller, I get a 406 response, and when I handle the html, it sends back the rendered page as ajax data...I think...

[gauravpant99]

I am facing a similar kind of problem where the same code is working fine in staging but not working in production .Both environment has same gems installed . I am using a rails version 3.0.10.

In production , the GET request is processes as a html but in staging it is processed as js .I have defined the respond_to for js format . I am no sure the reason for the same .
Also I have tried adding the defaults format as js in the routes.rb but that also is not working.

Below is the log for production and staging .

Production :

Started GET "/releases/cycle_paginate/2?id=4" for 10.30.10.67 at Wed Aug 14 07:13:45 -0400 2013
Processing by ReleasesController#cycle_paginate as JS
Parameters: {"id"=>"4", "page"=>"2"}

Staging :

Started GET "/releases/cycle_paginate/2?id=53" for 10.30.10.67 at Wed Aug 14 06:42:45 -0400 2013
Processing by ReleasesController#cycle_paginate as HTML
Parameters: {"id"=>"53", "page"=>"2"}

Appreciate if any one have a clue on this .