You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
looking at entries with process_action == hook, I noticed that the status is missing for entries that were redirected with the warden middleware. For redirects within my application with redirect_to, status is correctly set to 302.
I'm not too familiar warden and influxdb-rails/ActiveSupport::Notifications, but my guess is that it's due to the fact that it's another middleware.
request_id is empty because it's set by a monkey patch in the application controller which we never hit in this case. The status is pulled from the process-action-action-controller event which we seem to receive just without the status.
I will have a look into it but at this point I'm not sure we can do much about this 🤔
Hello again,
looking at entries with
process_action
==hook
, I noticed that thestatus
is missing for entries that were redirected with the warden middleware. For redirects within my application withredirect_to
,status
is correctly set to302
.I'm not too familiar warden and influxdb-rails/ActiveSupport::Notifications, but my guess is that it's due to the fact that it's another middleware.
If I understand correctly this is the code that does the actual redirect when a user is for example not authenticated:
https://github.com/heartcombo/devise/blob/main/lib/devise/failure_app.rb
Greetings,
Michael
The text was updated successfully, but these errors were encountered: