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 noticed that the GoogleLogin view throws a 500 error under certain input conditions. Specifically:
If both access_token and code are sent together in the request, the server crashes with a 500 error.
If an invalid access_token is sent on its own, it also results in a 500.
This happens consistently and seems like the view isn’t handling these edge cases gracefully. Here’s what my view looks like:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey there 👋
I noticed that the GoogleLogin view throws a 500 error under certain input conditions. Specifically:
If both access_token and code are sent together in the request, the server crashes with a 500 error.
If an invalid access_token is sent on its own, it also results in a 500.
This happens consistently and seems like the view isn’t handling these edge cases gracefully. Here’s what my view looks like:
Ideally, these should return a 400 Bad Request or a meaningful validation error instead of a server error.
🔍 Example Inputs That Trigger 500
Case 1: Sending both access_token and code
Case 2: Sending only an invalid access_token
Both of these cases consistently return a 500 response.
If you're open to it, I’d be happy to try fixing it and submit a PR 😊 Let me know!
Beta Was this translation helpful? Give feedback.
All reactions