Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

403 clicking "fix credit card" in email when not logged in #4040

Closed
JVimes opened this issue May 19, 2016 · 8 comments
Closed

403 clicking "fix credit card" in email when not logged in #4040

JVimes opened this issue May 19, 2016 · 8 comments

Comments

@JVimes
Copy link

JVimes commented May 19, 2016

My credit card expired and I got the email reminding me to fix payment info. I clicked the "fix credit card" button in the email and was taken to a 403 Forbidden page. Would expect to be taken to login form when I'm not already logged in. Thanks!

@mattbk
Copy link
Contributor

mattbk commented May 20, 2016

I think the behavior should be something like https://gratipay.com/new when a ~user is not logged in, would that work, @JVimes?

image

rather than

image

@JVimes
Copy link
Author

JVimes commented May 26, 2016

@mattbk, sorry for delay. That would be better, but could the styling for the 401 page be customized to put the emphasis on login rather than the HTTP status code? End users aren't concerned with the 401 status, they just want to be presented with the login form as soon as possible.

@mattbk
Copy link
Contributor

mattbk commented May 26, 2016

Probably. Glad you're paying attention--I don't even look at anything in the header anymore.

mattbk added a commit that referenced this issue Nov 13, 2016
Copied from 401.spt. Closes #4040.
@mattbk
Copy link
Contributor

mattbk commented Nov 13, 2016

Not as complicated as #4040 (comment) lays out. There was no 403.spt file, so no special page was shown.

@chadwhitacre
Copy link
Contributor

Shouldn't we be raising 401 in this case instead of 403?

401 = not logged in
403 = already logged in but still not allowed

@mattbk
Copy link
Contributor

mattbk commented Nov 18, 2016

401 = not logged in
403 = already logged in but still not allowed

Then why do I get 403 when not logged in, for pages like this?
image

@chadwhitacre
Copy link
Contributor

Because we're doing it wrong? :)

Unless we're not, but I think we are ...

https://httpstatuses.com/401
https://httpstatuses.com/403

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

No branches or pull requests

3 participants