rack-cache | Real HTTP Caching for Ruby Web Apps | Caching library

Ok looks like I have figured out the problem. But still not sure about it.

So after miserably failing with trying almost every site map generator I decided to create my own sitemap generator using Ruby Gems Nokogiri and Mechanize. But to my surprise whenever I would try to extract HTML code from my website the same error would show up "422 Unprocessable Entity". This was the exact error message which I was getting from a few Site map generators.

I removed "protect_from_forgery with: :exception" from Applications controller and the sitemap generators started working on my website.

But this wasn't right because "protect_from_forgery with: :exception" should be there. And I have 2 other websites with "protect_from_forgery with: :exception" included in the Application controllers. Sitemap Generators don't show any problem working with these 2 websites.

The only difference between my first website and the other 2 was that my first website was using ajax and the other 2 were simple. So i finally I figured out that when I remove the format.js line from

The root of the problem seems to be bundler. What operating system and Ruby version are you using? It may be a problem with old OpenSSL library, so you can not install bundler and everything after it.

If you are using jRuby (your gem list output tells so), your problem seems to be the same as described in link. And there is a solution as well.

Maybe you forgot to set 2.1.2 version of ruby as global? (rbenv set global 2.1.2)

You just shared the Gem file, but nothing how this app is developed, so it is insufficient information to give you an accurate response. But usually, two different methods are followed.

Two separate application, as your ruby on rails application working, can create another react application, and consume all endpoints present in your Ruby on Rails application, if you could not find some require endpoint, you can check already made endpoints and make few new one following the way. Hopefully, it would be easier to do.

In this method, you have to break apart your project and removing all Angular Gems already present in your project and start with fresh frontend with ReactJS. In my opinion, it requires much more Ruby on Rails knowledge to do it, but in the end, you will get just one project.

As from Gem file seem it is heavily using Angular, so probably you have run it and check if it has most of the Endpoints made Restful. If yes then I suggest to go on method one and create new ReactJS app, which will consume all endpoint made in Ruby on rails, that would be more work on React side app and less on Ruby on Rails. Even if you found that some endpoints are not present you can follow already created endpoints coding and action, where you will complete details. I understand there will be two different projects, but the learning curve to learn Ruby on Rails and integrating it with React would be more than having two different projects.

The exception:

Try running bundle update json to force update the json gem. If that doesn't work, you can run gem clean, delete your Gemfile.lock and run everything again.

Edit: It looks like your bundler version isn't compatible with your version of rails. You can try to downgrade bundler by running:

1. gem install bundler --version '1.14.6'
2. gem uninstall bundler --version '2.0.1'

Also, is this a new project? If so, you should consider using rails 5. Rails 3 is close to being three major versions behind with the release of rails 6 not too far away. It would help avoid a lot of these gem issues as well.

Switching from type :api to type :request gave me access to the request and response variables, which, before, I had to created variables myself to try access them.

When using type :api, I had access to last_response instead of response, because my type :api was including Rack::Test::Methods, which was messing up those variables (response and request), as according to this post.

When I switched to type :request, and was no longer importing Rack::Test::Methods, I was able to access request variable and saw that the desired headers were correctly added.

The problem is that Rails' subdomain method is very simple and doesn't know anything about the structure of com.au domains. For "admin.workninja.com.au" which you use on production, the subdomain method would return "admin.workninja". From the docs:

Returns all the \subdomains as a string, so "dev.www" would be returned for "dev.www.rubyonrails.org". You can specify a different tld_length, such as 2 to catch "www" instead of "www.rubyonrails" in "www.rubyonrails.co.uk".

And – without knowing your configuration– "admin.workninja" will very likely not match your config.workninja.admin_subdomain configuration anymore.

The solution is to configure a tld length of 2 on production. Just add the following to the configuration block in your config/environments/production.rb:

If you have rvm you may just install the latest ruby and rails. There is no need to use the system wide installed version.

https://rvm.io/gemsets/basics

I just use ruby 2.5.1 and rails 5.2.0.

Okay for some reason, , group: :production was added to gem 'redis-namespace', group: :production in the Gemfile. Removing group :production fixed the issue for me