Skip to content
New issue

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

StreamUtils.readString might return incorrect result #381

Closed
GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments
Closed

StreamUtils.readString might return incorrect result #381

GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 16, 2015

The implementation of StreamUtils.readString reads the contents of a Reader 
object into a String. The assumption is made that the single invoke of 
Reader.read always fills the entire buffer. Some readers do not support large 
(>8kb) buffers, resulting in incorrect results with 0X00 characters after the 
first 8192 characters. The solution is to respect the Reader.read() result and 
to keep reading until it returns -1.

Original issue reported on code.google.com by p.kruijsen on 30 Mar 2011 at 11:32

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

This issue has been fixed in revision r1905 (and r1906 for Maven branch).

Original comment by p.kruijsen on 30 Mar 2011 at 11:36

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

GoogleCodeExporter commented Mar 16, 2015

Original comment by qsieb...@gmail.com on 27 Jan 2012 at 10:58

  • Added labels: Release5.2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant