You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note the "×" in the name value. This gets accepted properly to the API and inserted into our database. However, httr errors out on the response with
Error in substring(u, so, so + ml - 1L) : invalid multibyte string, element 1
It seems that it can deal with the non-unicode character for posting to the API, but not in the response. Note that the response is encoded in utf-8. Doing the same POST with Postman poses no issues. Are there any ways to prevent this error ?
The text was updated successfully, but these errors were encountered:
httr has been superseded in favour of httr2, so is no longer under active development. If this problem is still important to you in httr2, I'd suggest filing an issue offer there 😄. Thanks for using httr!
I run httr::POST with the following to an API endpoint as JSON
Note the "×" in the name value. This gets accepted properly to the API and inserted into our database. However, httr errors out on the response with
It seems that it can deal with the non-unicode character for posting to the API, but not in the response. Note that the response is encoded in utf-8. Doing the same POST with Postman poses no issues. Are there any ways to prevent this error ?
The text was updated successfully, but these errors were encountered: