vetkit.ruby.rails.production-force-ssl-disabled

config.force_ssl is explicitly false in the production environment, so HTTPS, HSTS and secure cookies are not enforced by Rails.

Last updated: 2026-11-01

Suite: Security

ruby

config.force_ssl is explicitly false in the production environment, so HTTPS, HSTS and secure cookies are not enforced by Rails.

Category: SECURITY · Engine rule severity: INFO

How to fix it

Set config.force_ssl = true (and config.assume_ssl = true behind a TLS-terminating proxy).

Rule pattern example

The engine’s matching pattern, not a confirmed exploit. Metavariables and ellipses describe matching syntax.

$CFG.force_ssl = false

References

https://guides.rubyonrails.org/configuring.html#config-force-ssl

Source: packages/engine/rules/sast/ruby.yml.

Generated from shipped rule definitions at build time. Matching is a review signal, not proof of exploitability. “generic” denotes text matching, not complete language or framework coverage. Runtime configuration and available tools affect whether a rule runs.