🚀 go-pugleaf

I'm doing a simple GET to a server, and the data portion of the get string
contains some \u0081 and \u0080 characters used for control.

Somewhere in the URL MyURL = new URL(".. get operation");          the Java
runtime is converting these characters to x3F.  This is some sort of
encoding conversion, because the range of values between x80 and x9F is
reserved for other Unicode mischief.

I had a similar problem with a binary datastream for a barcode.  There, the
string contained characters in the above range and the default process
converted them all to x3F's.

I solved that problem by using the little known (but loved)  "8859_1"
encoding when converting MyString to bytes.

                                 MyString.getBytes("8859_1"),

The default CharToByteConverter was clearly performing the same unicode
translation, and by explicity specifying 8859_1 encoding, the conversion
maintained the integrity of the x80 through x9F values.


My question is:  How do I perform the analgous "fix" to the URL() API?   I
presume that somewhere in the process of transmitting my GET string to the
server, a default encoding is being used.  If I can somehow establish the
encoding as 8859_1 on that process, I'll bet my message gets through as
intended.  But I don't see anywhere in the API, or the URL() source code,
where one has the ability to do this.

This is a HARD one!   Anyone have any thoughts?

Best

Harry