Repository navigation
Getting invalid status code in Rails 8.0.2 #1477
Description
Hi team,
I’m using jsonapi-resources in a Rails application that we’re upgrading to Rails 8 (Ruby 3.3.x).
With versions 0.9.12 and 0.10.1, basic CRUD operations work, but error handling and validation responses are broken — for example, validation errors return status 0 instead of 422, and ActionController::ForceSSL raises uninitialized constant errors since it’s no longer included in Rails 8.
Could you please confirm if Rails 8 compatibility is planned, or if there’s an active branch/fork that supports newer Rails versions?
Thanks for maintaining this great gem!
Activity
takaokouji commentedon Nov 10, 2025
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.
prabha1988 commentedon Nov 12, 2025
Thanks for the update! 👍
Got it — I’ll try out speee#1 and verify on my side.
Fix ActionController::ForceSSL compatibility with Rails 8.0+
takaokouji commentedon Jan 21, 2026
We've addressed the ActionController::ForceSSL compatibility issue in the speee fork.
Fixed Issue: ActionController::ForceSSL was removed in Rails 8.0, causing
uninitialized constanterrors.Solution: Added proper existence checking before including the ForceSSL module:
Test Results on Rails 8.0.4:
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:
Merge pull request #23 from speee/fix/rails-8-forcessl-compatibility