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
I just dealt with a minor annoyance for an hour, figured I would share in case it was valuable for docs. When passing the passReqToCallback argument to a strat, the "incoming" query params are accessible through req.params. In Express, query params come through on req.query. In the callback/handler in the google strategy, req.query stores a state and code key, which makes it seem as though req.query is being overwritten even when passReqToCallback is true. Happy to update docs as long as this confusion isn't based solely in my own denseness 👍 .
The text was updated successfully, but these errors were encountered:
Actually, I am not sure what I did (or if it ever worked, was tired when I did this), but this no longer even works for me. If I set passReqToCallback: true on the strategy, query comes through with state and code, but req.params comes through empty.
Hi,
I just dealt with a minor annoyance for an hour, figured I would share in case it was valuable for docs. When passing the
passReqToCallback
argument to a strat, the "incoming" query params are accessible throughreq.params
. In Express, query params come through onreq.query
. In the callback/handler in the google strategy,req.query
stores astate
andcode
key, which makes it seem as thoughreq.query
is being overwritten even whenpassReqToCallback
is true. Happy to update docs as long as this confusion isn't based solely in my own denseness 👍 .The text was updated successfully, but these errors were encountered: