Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

403 after sign in #1250

Closed
clash99 opened this issue Mar 8, 2017 · 4 comments
Closed

403 after sign in #1250

clash99 opened this issue Mar 8, 2017 · 4 comments

Comments

@clash99
Copy link
Contributor

clash99 commented Mar 8, 2017

Steps to reproduce the error

  • Sign in as existing user.

Actual behavior

  • Receiving 403.

Expected behavior

  • Would expect to be redirected to the dashboard.

If I hit refresh, I do get redirected to the dashboard and sign-in was successful.

This is a sporadic error I've received about a dozen times over the past 2 days. I just want to document it in case others are seeing the same thing. I'm unable to pinpoint the cause.

screenshot 2017-03-08 12 28 40

@dpalomino
Copy link

I haven't seen any 403 in te last couple of days. @amplifi do you know if we can see something in the logs?

@amplifi
Copy link
Contributor

amplifi commented Mar 10, 2017

@dpalomino There are sporadic 403 http responses on the POST to account/login/ in staging, demo, and production. This isn't an "error" necessarily; as far as the logs are concerned that's the appropriate behavior for invalid CSRF tokens. Django handles CSRF, so we'd have to check that it's being implemented correctly on the platform side.

@dpalomino
Copy link

I think we can close this issue for now. Please reopen if you think this is happening too frequently.

Thanks!

@SteadyCadence
Copy link

SteadyCadence commented Apr 26, 2017

I just had this happen to me on demo in Chrome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants