Actual header key uses dashes, not underscores. #143
Merged
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
Fix typos in README (helpful to folks hand-rolling clients).
|
Thanks @ragaskar!!! |
lynndylanhurley
added a commit
that referenced
this pull request
Feb 9, 2015
Actual header key uses dashes, not underscores.
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.
Was using this project today and am not planning on using the angular bits. While writing request specs for the behavior I noticed that all header keys use dashes, not underscores as the README implies. I probably missed a few, but hopefully this is good enough for folks who are using the README as a quickstart to figure out what header values they care about.