Remove redundant jsonlite default overrides.
Add NEWS item.
Standardize Content-Type capitalization

While apparently the header fields are supposed to be case insensitive,
 #142 shows at least some systems do not follow the spec properly.  So
we might as well standardize all uses of `Content-Type` in the same
way.
Add note to news about Content-Type
Fix broken merge

There was an extra block I missed when I was doing the merge
Cleanup setting content-type for raw POST bodies.

Recent body handling changes have (happily) started setting the content-type
header directly when encoding a body. However, in the case that the body was
simply raw bytes, and the content type was set outside of httr, that
information was being dropped. This change simply threads that information
through (and adds a test).
Merge pull request #139 from jeroenooms/jsonlite_fix

Remove redundant jsonlite default overrides.
Merge pull request #146 from jimhester/Content-Type

Standardize Content-Type capitalization
Use the mime package. Closes #148
No longer import from tools
Improve content-type handling with bodies.
Closes #140
Implement safe_callback().
Closes #144
Added function as_header to oauth1.0_token

Same default as before, but is param as_header = FALSE is added then it
adds as parameter to url.
Added demo for withings

A small demo on how to use as_header to access withings API.
Updated style and added news

Fixed some styles issues and added a bullet point to the news. Also
fixed a typo in params explanation.
Added function as_header to oauth1.0_token

Same default as before, but is param as_header = FALSE is added then it
adds as parameter to url.
Added demo for withings

A small demo on how to use as_header to access withings API.
Updated style and added news

Fixed some styles issues and added a bullet point to the news. Also
fixed a typo in params explanation.
Merge remote-tracking branch 'origin/master'

Conflicts:
	NEWS.md
Added news