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

Fix response handler #22

Merged
merged 2 commits into from
Nov 11, 2016
Merged

Conversation

mjsalinger
Copy link
Contributor

No description provided.

@mjsalinger mjsalinger closed this Jun 1, 2016
@mjsalinger mjsalinger deleted the fix-response-handler branch June 1, 2016 15:30
@mjsalinger mjsalinger restored the fix-response-handler branch June 1, 2016 15:31
@mjsalinger mjsalinger reopened this Jun 1, 2016
Copy link
Member

@maxtruxa maxtruxa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See review comments.

@@ -24,7 +24,7 @@
"dependencies": {
"bluebird": "^3.0.5",
"express": "^4.13.3",
"oauth2-server": "next",
"oauth2-server": "kinvey/node-oauth2-server#kinvey",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should probably stay at "next". 😉

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed..

@maxtruxa
Copy link
Member

Tests fixed with #33.

@mjsalinger
Copy link
Contributor Author

Rebased to remove some duplicate commits and incorporate latest changes to master. @maxtruxa, one final review?

res.set(response.headers);
res.redirect(location);
}
else {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Style-wise.. Are we going by the 1TBS

} else {

or Stroustrup?

}
else {

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The former...

@maxtruxa
Copy link
Member

@mjsalinger
Are we always using 302 to redirect? Even if so, it might be a good idea to support the other redirect codes.

  • 301
  • 302
  • 303
  • 307
  • 308

@mjsalinger
Copy link
Contributor Author

302 is the default used in the oauth2 spec.. Others are allowed, and I think that's a good idea to add support for, but I think that should be a separate PR for a future release.

@mjsalinger
Copy link
Contributor Author

Added issue #37 to track.

@mjsalinger mjsalinger merged commit b47f246 into oauthjs:master Nov 11, 2016
@mjsalinger mjsalinger deleted the fix-response-handler branch November 11, 2016 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants