Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Wrong response format #71

Open
michalkopacz opened this issue Dec 19, 2014 · 2 comments
Open

Wrong response format #71

michalkopacz opened this issue Dec 19, 2014 · 2 comments

Comments

@michalkopacz
Copy link

Hi,

OAuth2 specification describe in point 5.2. response format for invalid request.
But in AuthController::tokenAction if status code is beetwen 400 and 500, we return reposne in problem+json format, not in format from specification. Why?

I know that client can recognize content-type of response, but many OAuth2 clients recognize format from specification.
@michalkopacz michalkopacz mentioned this issue Jan 7, 2015
Merged
baptistemanson pushed a commit to baptistemanson/zf-oauth2 that referenced this issue Jan 24, 2015
@weierophinney
[zfcampus#71] Added note about Apache and encoded slashes
f60058e
baptistemanson pushed a commit to baptistemanson/zf-oauth2 that referenced this issue Jan 24, 2015
@weierophinney
Merge branch 'hotfix/71'
b241bb0 
Close zfcampus#71
@michalkopacz
Copy link
Author

resolved in #72

@weierophinney weierophinney mentioned this issue Dec 31, 2019
Open
@weierophinney
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools-oauth2; a new issue has been opened at laminas-api-tools/api-tools-oauth2#17.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@weierophinney @michalkopacz