Aaron Parecki

I don't see how a 3xx code makes any sense, since the followup request is made to the same URL, so it's not a redirect.

From what I can tell, the `application/x-www-form-urlencoded` content type implies UTF-8 encoding, so it is not needed to include the `charset`. https://url.spec.whatwg.org/#application/x-www-form-urlencoded https://url.spec.whatwg.org/#application/x-www-form-urlencoded

That's copy pasted from RFC6749, maybe @dickhardt remembers the context of adding that in the first place? https://www.rfc-editor.org/rfc/rfc6749.html#section-10.14

> I personally think it would be helpful to force client to send audience while requesting for a token so that the access token generated can be linked to a...

I am on board with moving the bulk of the explanation lower down like this.

Please see this PR: https://github.com/oauth-wg/oauth-v2-1/pull/223 Since RFC7591 defines the registry, I don't think it's a good idea to try to move the registry itself. But in the spirit of updating...

oh shoot, let me take a look...

Did you create the database first and add the config to `.env`? I just tried a fresh install and the migrate command seems to be working, although I get an...

I just pushed a change that stops clobbering the exception when running in the console, so you should see the actual error message from the database now. `SQLSTATE[HY000] [1049] Unknown...

I _think_ it will work right now if you enter `goku/iphone` in the Overland device ID setting.