-Basically anything that is missing to make those JSON libraries useful in real life...
-Also Crypto could use some more work. Encrypt/decrypt with easy string parameters. Luckily Walbus posted a decent one in the forums which would make a nice addition to PB!
-Speaking about HTTP... the base64encoder also encodes the ending NULL character which goes against any other base64 encoder (checked .NET and several online base64 encoder websites). At least the help file should mention this.
HTTP(S) SetHttpHeader, Status, Response
Re: HTTP(S) SetHttpHeader, Status, Response
Hi,
I don't understand this one. You tell the Base64 functions how many input bytes to encode, so it's your choice to include a NULL or not.-Speaking about HTTP... the base64encoder also encodes the ending NULL character which goes against any other base64 encoder (checked .NET and several online base64 encoder websites). At least the help file should mention this.
Re: HTTP(S) SetHttpHeader, Status, Response
Ok, then add a stringbase64encode, just like what happened with fingerprint incl encoding. Make it "basic" to use.