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
Currently Jumblr MultipartConverter uses default system encoding for message body (message.getBytes()), that could be 8859-1 on some systems. Scribe, at same time, always use UTF-8 for signature (message.getBytes("UTF-8")).
So, on a system with non-UTF8 encoding it fails to work. On Auth step, but anyway, it cannot prepare valid request for non-latin post on such JVM.
The text was updated successfully, but these errors were encountered:
splix
added a commit
to splix/jumblr
that referenced
this issue
May 8, 2014
Currently Jumblr
MultipartConverter
uses default system encoding for message body (message.getBytes()
), that could be8859-1
on some systems. Scribe, at same time, always use UTF-8 for signature (message.getBytes("UTF-8")
).So, on a system with non-UTF8 encoding it fails to work. On Auth step, but anyway, it cannot prepare valid request for non-latin post on such JVM.
The text was updated successfully, but these errors were encountered: