Getting invalid status code in Rails 8.0.2 #1477

Activity

1. takaokouji commented on Nov 10, 2025

   

   takaokouji

   on Nov 10, 2025

   Contributor

   More actions

   We try to fix it, so please try it: speee#1 .

   Sorry, our modificaitons are includes setting for Claude Code, Docker (docker compose). We are currently testing the modifications. Once testing is complete, we plan to create a PR with those excluded.
2. prabha1988 commented on Nov 12, 2025

   

   prabha1988

   on Nov 12, 2025

   Author

   More actions

   Thanks for the update! 👍
   Got it — I’ll try out speee#1 and verify on my side.
3. takaokouji

   added a commit that references this issue on Jan 21, 2026

   Fix ActionController::ForceSSL compatibility with Rails 8.0+

   ...

   8aaa814
4. takaokouji commented on Jan 21, 2026

   

   takaokouji

   on Jan 21, 2026

   Contributor

   More actions

   We've addressed the ActionController::ForceSSL compatibility issue in the speee fork.

   Fixed Issue: ActionController::ForceSSL was removed in Rails 8.0, causing uninitialized constant errors.

   Solution: Added proper existence checking before including the ForceSSL module:

   • Fix ActionController::ForceSSL compatibility with Rails 8.0+ (Issue #1477) speee/jsonapi-resources#23

   Test Results on Rails 8.0.4:

   • ✅ No ForceSSL NameError
   • ✅ Resource tests pass
   • ✅ Validation tests correctly return 422 status code

   Note on validation status code issue: We could not reproduce the "status 0" problem. All our validation tests correctly return 422 on Rails 8.0.4. This may have been fixed in other changes, or may require specific reproduction steps. If you have a reproducible test case, please share it.

   If you'd like to try the speee fork with Rails 8.0 support:

   • Repo: https://github.com/speee/jsonapi-resources
   • Installation instructions in README
5. takaokouji

   added a commit that references this issue on Jan 21, 2026

   Merge pull request #23 from speee/fix/rails-8-forcessl-compatibility

   ...

   0513b04
6. MichalBryxi commented on Nov 13, 2026

   

   MichalBryxi

   on Nov 13, 2026

   More actions

   #1501 makes the 0.9 line (release-0-9) work on Rails 7.0 through 8.1 and Ruby 3.4. That's the line apps still use when they're pinned through jsonapi-authorization (~> 0.9.0).

   Both problems in this issue are already fixed on release-0-9, but neither has been released:

   • Status 0 instead of 422: fixed by fix(rack 3): Fixes #1456 per #1457 #1462.
   • ActionController::ForceSSL: it's only included on Rails < 6.1.

   So what's needed is a 0.9.13. What #1501 adds beyond the earlier attempts:

   • Compared with Add Rails 7.1+ and Rails 8.x support #1480: that PR targets master (0.10). It doesn't help 0.9 users.
   • Compared with Rails 7.0-8.1 support (full version up) speee/jsonapi-resources#1 / Fix ActionController::ForceSSL compatibility with Rails 8.0+ (Issue #1477) speee/jsonapi-resources#23: those live in a fork, mixed with tooling changes. Rails 7.0 to 8.1 and Ruby 3.4 support for release-0-9 #1501 contains only the gem's own changes and targets upstream.
   • Fixes not covered elsewhere: Rails 7.2 removed ActiveSupport::Deprecation.warn, which made attribute :id and belongs_to raise NoMethodError. Also Ruby 3.4's csv, and Rack 3.1's :unprocessable_entity deprecation.
   • Proof: the gem's own suite now passes on Rails 7.0, 7.1, 7.2, 8.0 and 8.1.4.1 (Ruby 3.2 and 3.4), and still on 5.1 to 6.1 (Ruby 2.6 and 2.7). The CI matrix runs all of them, so it stays checked.