Callback fails to run if request parameters are in the wrong order about rocket_oauth2 HOT 4 CLOSED

This is explained by the Rocket guide, but it's not easily "guessable" that TokenRequest uses Cookies. The current message Warning: The OAuth2 state returned from the server did not match the stored state. is misleading. I will definitely change that to something like Error: Unable to access request cookies. Is a Cookies guard already active?

probably nothing that documentation can't manage.

Do you have any suggestions on where to put this documentation? As in, the API docs for TokenResponse, the top-level documentation/examples, or in the examples/ directory?

from rocket_oauth2.

I can see it fitting in all of those places, but the top-level docs/examples and API docs for TokenResponse would be most visible I think.

from rocket_oauth2.

Alright, I made the following two changes:

• e0ed071 changes the log message for "cookie missing" vs "cookie mismatch". Unfortunately there's not a good way to distinguish "Cookies guard in the wrong order" from "the cookie is missing", so the error message is a "best effort".
• 7b825fe adds some explanation to the docs and doc examples.

I think this addresses your concerns.

from rocket_oauth2.

That looks fantastic, thanks!

from rocket_oauth2.