HttpClient extra UTF-8 decode problem?

[richardrega]

A few weeks back a came across a HTTP response map decode exception caused by a product description that has "... 100% ..." on.

The immediate fix was to simply encode this description string before making the API request with net.authorize.data.Order, but after some digging I found what might be an extra

URLDecoder.decode(responseString, HTTP.UTF_8);

richardrega@9155b3f

Can anyone else confirm this problem? I can provide more details if needed.

[KarthikeyanKumar]

Hello @richardrega ,

Team is looking into the problem and soon fix will be provided.

Thanks,
Karthikeyan

[vijayabraj]

Hi @richardrega , the URLDecoder.decode is done for reponse if transaction is of type (net.authorize.aim.Transaction or net.authorize.sim.Transaction) which is an old method of
integrating to our APIs. The java packages net.authorize.aim, net.authorize.sim will be deprecated soon and will not have newer updates.

You can check our sample codes repository to see the latest method provided by SDKs which are fully in sync with the latest updates to our APIs (refer: API reference). The controller and contract classes, being autogenerated, have less errors and are actively supported by us.

[chsriniv9]

@richardrega closing this issue based on the response from @vijayabraj . Please feel free to re-open if you need any further help.