Add support for passing in client URL / secret into the headers #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| headers['x-tagged-client-secret'] = req.secret; | ||
| } | ||
|
|
||
| console.info('post /api headers: ', headers); |
There was a problem hiding this comment.
This will be removed. Still doing some testing for now to make sure it works properly.
eviechan
force-pushed
the
add_mobile_spa_header
branch
from
f8da450
to
34caee6
Compare
eviechan
force-pushed
the
add_mobile_spa_header
branch
from
34caee6
to
82f4978
Compare
|
🍒 |
eviechan
added a commit
that referenced
this pull request
Feb 12, 2015
Add support for passing in client URL / secret into the headers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For Angular requests, passing in
clientIdis required. For server side requests,clientIdandsecretare required.