Base64 encoded zipFile in REST Response - Can it be handled in any way

[stefanostman]

Hi.
I have a problem. One of the HopTransformations I have created gets it input from a REST request. It has until now sent output as XML, but now suddenly changed to sending it as a base64 encoded Zip-fil containing the xml-document.
Any suggestions on how to handle it if it's even possible, I can't find a way.
Running HOP GUI version 2.15

[bamaer]

Just to be clear: this is not related to an Apache Hop; you were already running Hop 2.15.0 and the API response changed from plain XML to base64-encoded XML, correct?
If that is the case, the Calculator transform has a Base64 decode type that could help to decode your response to plain XML.

[stefanostman]

You are right that it is the API that charges not HOP. Problem is that it is not base64 encoded XML i get, but a Base64 encoded Zipfile containing one xml-document.
So what I think I need is something that can take the base encoded result from the REST and store it as a zip-file.

[bamaer]

not 100% sure if this will work, but what you could try is: accept the result from the REST client as a String, cast to binary with a Select Values (metadata tab), and write (only) that binary field to a file with a Text File Output (no header, no separator, no enclosing, US-ASCII or similar encoding)

[hansva]

I am going to assume the data you are getting is gzip base64 encoded data?
Here is a sample on how to decode the data you are getting within the pipeline.
base64zip.txt