🚀 go-pugleaf

Here's a bit more on what I'm trying to do.   I've created a little ISAPI
module called ISAPIUNICODE.DLL on the server noted below (you can hit this
if you want!).  When you  hit it with any type of data (RequestHEX), it will
simply return a string of 256 bytes starting from x00 through xFF.  I
created this little test DLL to isolate the conversion problem I'm having.

         String VPOURL2="http://38.168.115.174/isapi/isapiunicode.dll";
         System.out.println(VPOURL2.toString());

         URL url = new URL(VPOURL2);
         URLConnection uc = url.openConnection();
         uc.setDoOutput(true);
         uc.setDoInput(true);
         uc.setUseCaches (false);
         uc.setRequestProperty("Content-Type", "application/octet-stream");
         DataOutputStream dos = new DataOutputStream(uc.getOutputStream());
         // Send the data -- this seems to pass all of the hex information
with any Unicode issues!
         dos.write(RequestHEX);
         dos.flush();
         dos.close();

Now I try to capture these 256 bytes.  I've tried a number of approaches
(using bytes, ints, etc) , but let's take a very simple one:

         InputStreamReader MyInputStream = new
InputStreamReader(uc.getInputStream());
         BufferedReader drate= new BufferedReader(MyInputStream);
         StringBuffer response = new StringBuffer("");
         rateline = drate.readLine();   // production problem -- readline
will terminate when it encounters a \n or \r!!
         while(rateline != null) {
             response.append(rateline);
             rateline = drate.readLine();
         }
         System.out.println(response.toString());


If I inspect response in the debugger, I see:

             response[0] = \u0000;
             response[1]=  \u0001;
            ..................
             response[123]= \u007F;
             response[124]=\u20AC;   // should be byte x80
             response[125]=\uFFFD;
             .........
             response[155]=\u0178';  // should be byte x9F
             response[156]=\u00A0;
             response[157]=\u00A1;
             ...
             response[255]=\u00FF;


So my incoming message bytes are being "distorted" with the unicode
conversion in the range of \x80 through \x9F.

How can I avoid this?  I need to convert these simple byte values to
numbers, and when a number just happened to include a byte in the
aforementioned range, I can't evaluate the number correctly!