[英]SystemStackError (stack level too deep) - rendering JSON
使用 Rails API 构建。 提交 API 登录请求时出现错误SystemStackError (stack level too deep)
。
错误是围绕在此行上render json: {user: @user, token: token}.as_json, serializer: nil, :status =>:ok
尝试过的解决方案:
Ruby 2.4 和 Rails 4 堆栈级别太深 (SystemStackError)
https://github.com/rmosolgo/graphql-ruby/issues/2214
用户 controller:
class UsersController < ApplicationController
#auth_login only action to be authorized before an action
before_action :authenticate_request, only: [:auto_login, :edit]
def login
@user = User.find_by(email: params[:email])
if @user && @user.authenticate(params[:password])
token = encode_token({email: @user.email})
render json: {user: @user, token: token}.as_json, serializer: nil, :status => :ok
else
render json: {error: "Invalid email or password"}, :status => :unauthorized
end
end
private
def default_serializer_options
{
serializer: nil
}
end
end
该错误令人讨厌,因为它不一致。 有时它可以毫无问题地构建,有时则不会。 不确定 go 的位置,因为我看不到代码递归的任何地方。
更新:应用程序 Controller 与encode_token
class ApplicationController < ActionController::API
before_action :authenticate_request
def encode_token(payload)
JWT.encode(payload, 's3cr3t')
end
def auth_header
#requesting the header type of authorization (with token) that we will declare through our api requests
# { Authorization: 'Bearer <token>' }
request.headers['Authorization']
end
def decoded_token
if auth_header
#going to take the token and decode it
token = auth_header.split(' ')[1]
# header: { 'Authorization': 'Bearer <token>' }
begin
puts token
JWT.decode(token, 's3cr3t') #The header is sending the correct token but returning a fail.
rescue JWT::DecodeError
# puts "fail"
nil
end
end
end
def logged_in_user
#consults decode_token to check the header for valid information
if decoded_token
puts "Do"
email = decoded_token[0]['email']
@user = User.find_by(email: email)
end
end
def logged_in?
#returns true or false
!!logged_in_user
end
def authenticate_request
#consults logged_in? see see if user is authorized
render json: { message: 'Please log in' }, status: :unauthorized unless logged_in?
end
end
对于解决方案,我发现渲染@user 存在问题。 虽然我已经通过rake db:reset
等重置了数据库,但我需要重置 postgres。 之后,一切都按预期工作。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.