Android Question EncodeBase64 for URL and Files

It depends on the http request type and encoding. Simplest way is to send POST requests and read the raw payload.

If you need to send a GET request then use HttpJob.Download2. It will url encode the parameters.

Erel beat me to the punch, but I was 75% done and perhaps there's something useful here anyway, so:

Encode64 needs 64 distinct characters to encode 6 bits. 26 uppercase letters and 26 lower case letters and 10 digits = 62 characters, so two extra characters are needed. The B4X EncodeBase64 uses the MIME choice of "+" and "/", and "=" for padding at the end if there is not a whole number of 3 byte groups.

All three of those characters should be safe for use at the end of a URL, after the "?" here-come-the-parameters marker.

If you wanted to be sure, you could replace the characters with something else after encoding, and ditto in reverse before decoding.

Or there is this in StringUtils, maybe that's something to look at:



Or you could write your own EncodeBase52 that just uses letters, or EncodeBase32, or EncodeBase16... no, wait, that last one's already done:

Hello,

im using : (with me, the second setting for charge dont works, so i send like that )

So i have to make an encodeURL with all my PostSring charge values that i pass inside PSParams ?

an example of return : (with an /)

AppUserMpass : LButHLwoaq8jOd92jzY76oavNIbLwVguoY/qjYPkgRgfO7FLEzSAcw==

Note that the length of a url is limited. In your case you are all sending as get parameter which ends in a long url.
If you, for example upload a image (base64 encoded) you´ll most probably reach the maximum allowed url-length.

Check Google.

ALBRECHT said:

Return su.EncodeBase64(c.Encrypt(text.GetBytes("utf8"), password))

Click to expand...

I was shying away from using hexadecimal because it is easily recognisable and thus less obfuscative, but if you're actually doing real encryption, then disguising the encrypted data is less of a concern. If you're only talking small quantities of data, eg < few kBs on disk or < few hundred bytes over network, then HexFromBytes is a reasonable choice.

Just remember that it increases your data size by another 50% compared to Base64. And that disk/network space is cheap compared to your time ;-)

Ok

I send only small settings strings with PostString :


so I will opt for the encodeURL of my charge values : PSParams
(that will automaticaly replace the 62 + 63 code inside the base64 encoded param)

Thanks for all

ALBRECHT said:

I send only small settings strings with PostString

Click to expand...

You are NOT POSTing anything than an empty String.

I suggest to use PostMultipart where the Map should contain all your Values (PSParams) and an null for the Filelist.
You don´t need to urlencode anything

Ok i will try PostMultipart (and switch with post method)
because my values already come from a map

Thanks