We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
content
with httr v1.1.0 I now get No encoding supplied: defaulting to UTF-8. warning when a response class prints
httr v1.1.0
No encoding supplied: defaulting to UTF-8.
response
#> Response [http://api.crossref.org/journals/0413-6597] #> Date: 2016-01-29 00:25 #> Status: 404 #> Content-Type: text/plain #> Size: 19 B #> No encoding supplied: defaulting to UTF-8.
yet the user can't set encoding for the internal use of content() in print.response() here https://github.com/hadley/httr/blob/f7593b7d5b3f9396469d1220dd4b38206fbb7d2e/R/response.r#L57 - should this have content(x, "text", encoding = "UTF-8") instead? Or am i missing something
content()
print.response()
content(x, "text", encoding = "UTF-8")
The text was updated successfully, but these errors were encountered:
👍
Sorry, something went wrong.
+1
25557c0
No branches or pull requests
with
httr v1.1.0
I now getNo encoding supplied: defaulting to UTF-8.
warning when aresponse
class printsyet the user can't set encoding for the internal use of
content()
inprint.response()
here https://github.com/hadley/httr/blob/f7593b7d5b3f9396469d1220dd4b38206fbb7d2e/R/response.r#L57 - should this havecontent(x, "text", encoding = "UTF-8")
instead? Or am i missing somethingThe text was updated successfully, but these errors were encountered: