bundler-audit VS rack-cors

This Ruby gem is quite useful for detecting versions of gems that are known to be vulnerable to security issues. bundler-audit uses an open database of vulnerable gems called ruby-advisory-db and compares it to the versions that show up in your Gemfile.lock.

bundler-audit - check for known security issues

Let’s take the super famous gem bundler-audit, for instance. It works closely with bundler to provide patch-level verification for your project gems, such as vulnerability checks, insecure gem sources, etc.

For this, you can use the rack-cors gem:

Because the origin is not matching. For testing purposes you could use https://github.com/cyu/rack-cors.

Have you enabled cors in the rails app? https://github.com/cyu/rack-cors

# Be sure to restart your server when you modify this file. # Avoid CORS issues when API is called from the frontend app. # Handle Cross-Origin Resource Sharing (CORS) in order to accept cross-origin AJAX requests. # Read more: https://github.com/cyu/rack-cors Rails.application.config.middleware.insert_before 0, Rack::Cors do allow do origins 'http://データを贈りたいパス' resource '*', headers: :any, methods: [:get, :post, :put, :patch, :delete, :options, :head] end end

You'll also want to make sure your Rack CORS setup is taken care of. In the Gem file, you'll need to install the cors gem which can be found here. After adding to your Gem file, make sure to run bundle install from your command line again.

Have the following in my /config/initializers/cors.rb and using rack-cors gem